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 ammar2
Recipients The Compiler, ammar2, vstinner
Date 2017-07-23.21:20:26
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1500844826.71.0.262646612213.issue30998@psf.upfronthosting.co.za>
In-reply-to
Content
As the faulthandler documentation notes: 

> The fault handler is called on catastrophic cases and therefore can only use signal-safe functions (e.g. it cannot allocate memory on the heap). Because of this limitation traceback dumping is minimal compared to normal Python tracebacks:

This immediately disqualifies glibc's backtrace function as it is explicitly marked as AS-Unsafe.

The Windows code you linked also has a heap allocation, it isn't open source like backtrace but I'd imagine its implementation is fairly complex underneath.

Overall, adding more complexity especially to a handler dealing with a catastrophic failure is generally not a very good idea and it's really not a trivial problem to have easy cross platform stack traces. As much as I like this idea I don't think implementing is going to be possible and this is one of the points where you just have to attach a debugger like gdb for good information.
History
Date User Action Args
2017-07-23 21:20:26ammar2setrecipients: + ammar2, vstinner, The Compiler
2017-07-23 21:20:26ammar2setmessageid: <1500844826.71.0.262646612213.issue30998@psf.upfronthosting.co.za>
2017-07-23 21:20:26ammar2linkissue30998 messages
2017-07-23 21:20:26ammar2create