When an exception reaches the top frame and is displayed by the exception handler, they are handled by formatting them to stderr.  This involves a series of calls to PyFile_WriteString, either directly from PyErr_Display or indirectly through PyTraceBack_Print.  Few, if any, of these PyFile_WriteString calls have their result checked for error.  Worse, PyFile_WriteString itself does not check the return value of fputs().

So, for example, with a signal handler installed, a signal received while a traceback is being printed can result in the traceback _not_ being printed.

I don't suppose you could wrangle up a proposed patch to fix this?

Not likely, given the number of things on my plate already.

Ok, thanks JP.

Georg recently touched one of these functions and seemed to do the right
thing with respect to checking errors, so I've assigned it to you.  Can
you take this?

I'll look into it.

Surely it's not a good idea to attempt to generate an exception within
an exception handler, couldn't this lead to an infinite loop scenario?

The checks prior to fputs() handle any errors by calling err_closed()
and returning -1. I suggest we do the same for the fputs() statement.
According to the documentation for fputs(), any errors result in a
return value of EOF, therefore an if(fputs(...) == EOF) { ... } check
seems appropriate.

I enclose a patch to this end, please let me know whether I'm way off
the mark here :-)

The attached patch doesn't fix the issue I described:

  * err_closed() will raise an exception indicated the file is closed. 
However, the file is not necessarily closed, so this exception is wrong.
  * Most or all PyFile_WriteString callers are still not checking its
return value, so the exception will generally be ignored.
  * The traceback still won't be reported.

Ok, thankyou for your feedback, I will take another look at it.

I don't see anything "easy" in this issue.  Error handling in exception or signal handlers is quite tricky.

I don't see this as a high priority either, but will leave this for others to decide.

This is certainly a low-priority issue, as it will almost never happen in practice.

I think this can be closed as out of date because PyFile_WriteString/Object no longer use puts and they do check for errors. The error checking of PyFile_WriteString/Object in the traceback display code was the subject of Issue45635.