This is the mail archive of the
libc-alpha@sources.redhat.com
mailing list for the glibc project.
Re: get/set/swapcontext + linuxthreads/glibc + MTasker
- From: Ulrich Drepper <drepper at redhat dot com>
- To: Roland McGrath <roland at redhat dot com>
- Cc: bert hubert <ahu at ds9a dot nl>, libc-alpha at sources dot redhat dot com, phil-list at redhat dot com
- Date: Fri, 17 Jan 2003 21:18:12 +0000
- Subject: Re: get/set/swapcontext + linuxthreads/glibc + MTasker
- Organization: Red Hat, Inc.
- References: <200301172105.h0HL56V31263@magilla.sf.frob.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Roland McGrath wrote:
> You can use sigaltstack for each thread with N separate signal stacks.
There is no wording in the standard whether the signal stack is a
process or thread property. The former makes no sense but this would
"only" require not allowing the use of sigaltstack in multi-threaded
apps. I've an interpretation request outstanding.
In any case, no portable application can use it anyway since this is in
the standard:
Use of this function by library threads that are not bound to
kernel-scheduled entities results in undefined behavior.
- --
- --------------. ,-. 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)
iD8DBQE+KHMU2ijCOnn/RHQRAqXsAJ90F6AxEbgk2nCDZZ2uV9hLqm0qZACgk3wD
VIqL9q8XJF6LwIBzzu86wNk=
=Tlmt
-----END PGP SIGNATURE-----