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

Antoine Pitrou report at bugs.python.org
Wed Oct 13 18:45:40 CEST 2010


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

> I am then confused by this in the initial comment:
> 
> > It calls indirectly PyUnicode_EncodeUTF8() and so call
> > PyBytes_FromStringAndSize() which allocates memory on the heap.
> 
> I've not studied the patch though, so this may have changed.

The patch certainly has changed, yes. In the latest patch, printing of
unicode message is done one code point at a time without allocating any
intermediary area.

----------

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


More information about the Python-bugs-list mailing list