homepage

Serhiy Storchaka added the comment:
> The second (exception == NULL) check in _Py_PrintFatalError() looks suspicious. When it is possible? And if it is possible, can it cause leaks?
Sorry, I have no idea. I didn't write this code myself. It comes from
PyErr_PrintEx():
 PyErr_Fetch(&exception, &v, &tb);
 if (exception == NULL)
 return;
 PyErr_NormalizeException(&exception, &v, &tb);
 if (tb == NULL) {
 tb = Py_None;
 Py_INCREF(tb);
 }
 PyException_SetTraceback(v, tb);
 if (exception == NULL)
 return;
I read again PyErr_NormalizeException(). I'm not sure that the case
can occur in practice. Maybe it can be replaced with an assertion?
Since Py_FatalError() is called in catastrophic cases, I chose to not
try to drop safety checks :-) You can modify PyErr_PrintEx() or even
_Py_PrintFatalError() if you feel more brave than me :-D