tree 56af572633ecdd0d3187d7bdbc02fbf68d08d578
parent 1f62380a2e85caf3118568c4fb0bdea32d7e2ba1
author Brad Bishop <bradleyb@fuzziesquirrel.com> 1654043524 -0400
committer Brad Bishop <bradleyb@fuzziesquirrel.com> 1654540111 -0400

main: Add unhandled exception debug information

In general destructors should not throw exceptions because they are
possibly already being run during stack unwind from a previous
exception.  In those situations the process will terminate with no
opportunity for gracefully handling errors.

For the more typical case of primary exceptions during deconstruction,
the exceptions coming out of sendIntrospectionCompleteSignal are
unknown, so catch them, log them, and then terminate the process.  Over
time as the errors coming out of sendIntrospectionCompleteSignal are
discovered, those errors can be added to a set of expected errors that
need not terminate the process.

In the end, the behavior is only moderately changed - prior to this
patch this exception would already propagate and the application
terminate.  The new behavior here is simply to make a note that it
occurred, and to provide some guidance (this message) to whoever gets
the bug when sendIntrospectionCompleteSignal inevitably does fail and
throw an error.

Also, this makes clang happy (bugprone-exception-escape).

Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Change-Id: I67c11c732b3179afcf7174b6f09025083000b85b