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 dmalcolm, pitrou, vstinner
Date 2010-10-13.11:10:12
SpamBayes Score 7.46876e-07
Marked as misclassified No
Message-id <>
> dmalcolm asked if it would be possible to display the 
> Python backtrace on Py_FatalError()

It works :-) I fixed a bug in ceval.c (r85411) which was not directly related.

Patch version 5:
 - Display the Python backtrace on Py_FatalError() (if no error occurred)
 - Use _PyThreadState_GetFrame(tstate) instead of tstate->frame
 - Create _Py_DumpBacktrace() function
 - _Py_DumpBacktrace() doesn't display anything if there is no frame (tstate->frame == NULL), it's the case during Python initialization
 - replace fprintf() by calls to fputs/fputc in Py_FatalError(): fprintf() might raise a new error, I prefer simple functions (safer and faster)
Date User Action Args
2010-10-13 11:10:18vstinnersetrecipients: + vstinner, pitrou, dmalcolm
2010-10-13 11:10:18vstinnersetmessageid: <>
2010-10-13 11:10:16vstinnerlinkissue8863 messages
2010-10-13 11:10:16vstinnercreate