Remove the abort handler in the backtrace generator
The abort handler in the backtrace generator calls
exit(3) which is not asynchronous-signal-safe. Calling
exit(3) in this context is undefined behavior according to the C standard. See https://www.securecoding.cert.org/confluence/x/34At for more information.
FWICT the handler is meant to force the backtrace generator to always have an zero exit code. How the generator is currently used its exit code does not matter so the handler can probably be removed.
Patch coming soon after some testing.