|
From: Paul M. <pa...@sa...> - 2005-11-16 22:53:29
|
Julian Seward writes: > So all this works fine, the signal handler runs, but when the handler > returns there's a problem: it returns to a 2-insn trampoline in the > stack (created by stack_mcontext in sigframe-ppc32-linux.c). And that > stack is in the bss and so is marked non-executable, and V notices that, > and refuses to run that code, declaring a segfault instead. Then it > all goes to hell. I'm surprised you get that far, considering that the PLT is in the BSS and the PLT contains executable code trampolines. :) > - can anyone familiar with LinuxThreads internals comment on whether > my inferences about the manager thread stack are correct? Sounds reasonable. > - should we be creating a bss segment which is executable as well as > r/w-able? For ppc32, yes. Paul. |