➜

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 Albert.Zeyer
Recipients Albert.Zeyer, vstinner
Date 2016-03-26.00:13:55
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1458951235.27.0.732627449305.issue23886@psf.upfronthosting.co.za>
In-reply-to
Content 
Yes exactly. Sorry if I was unclear before. :)

I mentioned SIGUSR1/2 because for a segfault, the signal handler will usually be executed in the same thread (although I'm not sure if that is guaranteed), so that was usually not a problem. But I used SIGUSR1 when my Python application is hanging and esp in that case I would like to know the current Python active thread.
History
Date User Action Args
2016-03-26 00:13:55Albert.Zeyersetrecipients: + Albert.Zeyer, vstinner
2016-03-26 00:13:55Albert.Zeyersetmessageid: <1458951235.27.0.732627449305.issue23886@psf.upfronthosting.co.za>
2016-03-26 00:13:55Albert.Zeyerlinkissue23886 messages
2016-03-26 00:13:55Albert.Zeyercreate