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.

作者 pitrou
收信人 mark.dickinson, nnorwitz, pitrou, r.david.murray, srid
日期 2009-10-29.14:53:10
SpamBayes Score 0.0004898072
Marked as misclassified
Message-id <1256827993.09.0.403679736015.issue4970@psf.upfronthosting.co.za>
In-reply-to
内容
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?)
历史
日期 用户 动作 参数
2009-10-29 14:53:13pitrou修改recipients: + pitrou, nnorwitz, mark.dickinson, r.david.murray, srid
2009-10-29 14:53:13pitrou修改messageid: <1256827993.09.0.403679736015.issue4970@psf.upfronthosting.co.za>
2009-10-29 14:53:11pitrou链接issue4970 messages
2009-10-29 14:53:10pitrou创建