This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: Speaking of sigaltstack...
- From: Steven Munroe <sjmunroe at us dot ibm dot com>
- To: libc-alpha at sources dot redhat dot com
- Date: Mon, 10 Feb 2003 09:59:36 -0600
- Subject: Re: Speaking of sigaltstack...
- Organization: IBM Linux Developement
Tom Gall Writes:
> It would appear that in linuxthreads when the pthread signal handler
> wrapper gets control in the manager thread, and calls thread_self, it
> gets the alternate stack and BOOM, that's all she wrote.
This might be related to if the platform has floating stacks or not.
Platforms that don't have floating stacks (i386 and ppc in glibc-2.2.5)
use the stack pointer to infer the location of struct pthread_descr. For
the thread manager to (or any linuxthread function that uses
thread_self) to finding the signal stack instead of the original thread
stack will break this dependency.
Platforms that have floating stacks (ppc64, ia64) should be OK.