[issue8863] Display Python backtrace on SIGSEGV, SIGFPE and fatal error

[Antoine Pitrou]

Antoine Pitrou <pitrou at free.fr> added the comment:

> You would be wise to avoid using heap storage once you're in the crash
> handler. From a security standpoint, if something has managed to
> damage the heap (which is not uncommon in a crash), you should not
> attempt to allocate or free heap memory.

As far as I can tell, the signal handler in the patch doesn't call
malloc() or free(), neither directly nor indirectly.

----------

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue8863>
_______________________________________