Message 16490 - 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	langmead
Recipients
Date	2004-05-10.18:45:02
SpamBayes Score
Marked as misclassified
Message-id
In-reply-to

Content
Logged In: YES user_id=119306 Unfortunately, in pthreads the "synchronous" doesn't apply to a signal number, but its method of delivery. You can deliver a "SIGSEGV" asynchronously with the "kill" command, and you send normally asynchronous signals with pthread_kill. What <http:// sourceforge.net/tracker/ ?func=detail&aid=949332&group_id=5470&atid=305470> does is unblock signals like SIGSEGV which are likely to be sent synchronously from the OS and are unlikely to be handled by normal processes as asynchronous handlers.

Logged In: YES 
user_id=119306

Unfortunately, in pthreads the "synchronous" doesn't apply to a 
signal number, but its method of delivery. You can deliver a 
"SIGSEGV" asynchronously with the "kill" command, and you send 
normally asynchronous signals with  pthread_kill. What <http://
sourceforge.net/tracker/
?func=detail&aid=949332&group_id=5470&atid=305470> does is 
unblock signals like SIGSEGV which are likely to be sent 
synchronously from the OS and are unlikely to be handled by 
normal processes as asynchronous handlers.

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