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 ncoghlan
Recipients brian.curtin, jkloth, larry, ncoghlan, pitrou, vstinner
Date 2013-08-03.12:45:44
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1375533944.84.0.73911843883.issue18396@psf.upfronthosting.co.za>
In-reply-to
Content
I checked the getsignal docs, and indeed None is the expected return value for "signal handler exists, but was not installed from Python". That's accurate given the way faulthandler works:

On Linux (Python 3.3.0):

$ python3 -c "import signal; print(signal.getsignal(signal.SIGSEGV))"
0
$ python3 -X faulthandler -c "import signal; print(signal.getsignal(signal.SIGSEGV))"
None

So Jeremy's patch looks correct to me - when faulthandler is enabled, we need to skip over the signals that have those handlers attached.
History
Date User Action Args
2013-08-03 12:45:44ncoghlansetrecipients: + ncoghlan, pitrou, vstinner, larry, jkloth, brian.curtin
2013-08-03 12:45:44ncoghlansetmessageid: <1375533944.84.0.73911843883.issue18396@psf.upfronthosting.co.za>
2013-08-03 12:45:44ncoghlanlinkissue18396 messages
2013-08-03 12:45:44ncoghlancreate