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 vstinner
Recipients amaury.forgeotdarc, davidfraser, dmalcolm, joshbressers, pitrou, vstinner
Date 2010-12-20.00:12:31
SpamBayes Score 0.00058848434
Marked as misclassified No
Message-id <1292803958.73.0.767943098822.issue8863@psf.upfronthosting.co.za>
In-reply-to
Content
Version 10 of my patch:
 - the fault handler restores the previous signal handler instead of calling (DebugBreak() and) abort(): the previous signal handler will be called later to keep the orignal behaviour
 - _testcapi.sigill() and _testcapi.sigbus() send SIGILL/SIGBUS signal in an unlimited loop instead of sending the signal once. So the signal is sent again after calling the Python signal handler, and the previous signal handler is called
 - (minor change) use 2 arrays (fault_handlers and fault_signals) for all signals, instead 2 variables (xxx_enabled, xxx_handler) for each signal

With this patch, the original signal handler is called and so the Python fault handler is compatible with OS fault handlers like grsecurity and Apport.
History
Date User Action Args
2010-12-20 00:12:38vstinnersetrecipients: + vstinner, amaury.forgeotdarc, davidfraser, pitrou, dmalcolm, joshbressers
2010-12-20 00:12:38vstinnersetmessageid: <1292803958.73.0.767943098822.issue8863@psf.upfronthosting.co.za>
2010-12-20 00:12:32vstinnerlinkissue8863 messages
2010-12-20 00:12:32vstinnercreate