Message 94670 - Python tracker

➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author	pitrou
Recipients	mark.dickinson, nnorwitz, pitrou, r.david.murray, srid
Date	2009-10-29.14:53:10
SpamBayes Score	0.0004898072
Marked as misclassified	No
Message-id	<1256827993.09.0.403679736015.issue4970@psf.upfronthosting.co.za>
In-reply-to

Content
Prelude has had the same problem with signal 32: https://dev.prelude-ids.com/issues/show/133 According to their research, it is due to the linuxthreads implementation of the pthread API. To know which threads implementation your glibc is using, you can run "getconf GNU_LIBPTHREAD_VERSION" (on a modern system, it should print something like "NPTL 2.9"). (of course, the question is, since the signal is used by linuxthreads, why doesn't it get caught instead of killing the process?)

Prelude has had the same problem with signal 32:
https://dev.prelude-ids.com/issues/show/133
According to their research, it is due to the linuxthreads
implementation of the pthread API.

To know which threads implementation your glibc is using, you can run
"getconf GNU_LIBPTHREAD_VERSION" (on a modern system, it should print
something like "NPTL 2.9").

(of course, the question is, since the signal is used by linuxthreads,
why doesn't it get caught instead of killing the process?)

History
Date	User	Action	Args
2009-10-29 14:53:13	pitrou	set	recipients: + pitrou, nnorwitz, mark.dickinson, r.david.murray, srid
2009-10-29 14:53:13	pitrou	set	messageid: <1256827993.09.0.403679736015.issue4970@psf.upfronthosting.co.za>
2009-10-29 14:53:11	pitrou	link	issue4970 messages
2009-10-29 14:53:10	pitrou	create