STINNER Victor <victor.stin...@haypocalc.com> added the comment: > 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) ---------- Added file: http://bugs.python.org/file19214/segfault_handler-5.patch _______________________________________ Python tracker <rep...@bugs.python.org> <http://bugs.python.org/issue8863> _______________________________________ _______________________________________________ Python-bugs-list mailing list Unsubscribe: http://mail.python.org/mailman/options/python-bugs-list/archive%40mail-archive.com
