Message 16484 - 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.

Recipients
Author	langmead
Date	2004年05月07日.13:48:50
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=119306 There are two different thread related patches that I submitted, I agree that <http://sourceforge.net/tracker/? func=detail&aid=948614&group_id=5470&atid=305470> is pretty radical. (Its the one that tests at configure time for LinuxThreads peculiarities and alters the thread spawning and signal related activities accordingly.) A different related signal patch <http://sourceforge.net/tracker/? func=detail&aid=949332&group_id=5470&atid=305470> might be more appealing to you. It only unblocks signals like segmentation faults that creates synchronously sends to itself and that a pthreads implementation will always send to the faulting thread. (whether it blocks it or not.)

Content

Logged In: YES 
user_id=119306
There are two different thread related patches that I submitted,
I agree that 
<http://sourceforge.net/tracker/?
func=detail&aid=948614&group_id=5470&atid=305470> is pretty radical. 
(Its the one that tests at configure time for LinuxThreads peculiarities 
and alters the thread spawning and signal related activities accordingly.)
A different related signal patch
<http://sourceforge.net/tracker/?
func=detail&aid=949332&group_id=5470&atid=305470> might be more 
appealing to you. It only unblocks signals like segmentation faults that 
creates synchronously sends to itself and that a pthreads implementation 
will always send to the faulting thread. (whether it blocks it or not.)

History
Date	User	Action	Args
2007年08月23日 14:14:05	admin	link	issue756924 messages
2007年08月23日 14:14:05	admin	create

homepage