➜

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 neologix
Recipients mark.dickinson, neologix, nnorwitz, pitrou, r.david.murray, skrah, srid
Date 2010-04-13.12:03:27
SpamBayes Score 3.1096483e-06
Marked as misclassified No
Message-id <1271160209.0.0.02613812488.issue4970@psf.upfronthosting.co.za>
In-reply-to
Content 
Signal 32 is the first real-time signal, and is indeed used by linuxthreads, so it's very likely a linuxthreads bug, since this signal shouldn't leak to application.
Since linuxthreads is no longer maintained, I'm afraid we can't do much about this, except check for the threading library used and say "linuxthreads is obsolete and has known issues - please upgrade your system for reliable threading support".
History
Date User Action Args
2010-04-13 12:03:29neologixsetrecipients: + neologix, nnorwitz, mark.dickinson, pitrou, r.david.murray, srid, skrah
2010-04-13 12:03:29neologixsetmessageid: <1271160209.0.0.02613812488.issue4970@psf.upfronthosting.co.za>
2010-04-13 12:03:27neologixlinkissue4970 messages
2010-04-13 12:03:27neologixcreate