This is the mail archive of the
mailing list for the glibc project.
Re: get/set/swapcontext + linuxthreads/glibc + MTasker
- From: Ulrich Drepper <drepper at redhat dot com>
- To: bert hubert <ahu at ds9a dot nl>
- Cc: libc-alpha at sources dot redhat dot com, phil-list at redhat dot com
- Date: Fri, 17 Jan 2003 11:24:31 +0000
- Subject: Re: get/set/swapcontext + linuxthreads/glibc + MTasker
- Organization: Red Hat, Inc.
- References: <20030117111609.GA3963@outpost.ds9a.nl>
-----BEGIN PGP SIGNED MESSAGE-----
bert hubert wrote:
> Is there a fundamental reason why get/set/swapcontext and linuxthreads bite
In some configurations the stack pointer is used to identify the thread
pointer. Therefore it is impossible to reliably use the *context
functions together with LinuxThreads.
> Would this be a problem for NPTL?
Have you tried it? Me neither, but I don't see a problem.
> Any way to resolve this? Would using 'sigaltstack' help resolve this? Would
> using NPTL solve this?
Don't use sigaltstack in multi-threaded programs. Just think a second
about the desasters which would happen if two signals arrive at the same
time and are handled by different threads.
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
-----END PGP SIGNATURE-----