Apache OpenOffice (AOO) Bugzilla – Issue 17467
crash logger fails to catch abort()?
Last modified: 2003-11-26 09:52:04 UTC
I think assert(), raise(), and abort() raise a signal that is not caught by the crash logger. The program terminates abruptly, and no stack traceback is generated. On Unix/Linux, the workaround is to run the program under gdb, but the average user can't do that, nor can Windows users. issue 17368 is an example of a crash where I had to use gdb to get a traceback.
TM->JA: As TZ mentioned, you might have a look. Thanks !
JA: assert() and raise() don't make sense to me but it would be fine to activate the OOo sighandler if an abort() is thrown. Joost->Hennes: please check the source code if it's possible to add abort() to our sighandler. Changed target.
Accepted.
Thanks. This should be a trivial change -- just add SIGABRT to the list of signals that trigger the crash reporter, maybe. If it is that easy, it should be done sooner than OOo 2.0, IMHO, since I think there are a fair number of issues in IZ where OOo just terminates abruptly in this way.
this is no crash, thus removing dependency to issue 21786
crash reporter is raised by abort() in OOo 1.1.0.
Closed.