Issue 17467

Summary: crash logger fails to catch abort()?
Product: General Reporter: dankegel <dank>
Component: codeAssignee: hennes.rohling
Status: CLOSED FIXED QA Contact: issues@framework <issues>
Severity: Trivial    
Priority: P3 CC: frank.schoenheit, issues
Version: OOo 1.1 RC2   
Target Milestone: OOo 2.0   
Hardware: PC   
OS: Linux, all   
Issue Type: DEFECT Latest Confirmation in: ---
Developer Difficulty: ---

Description dankegel 2003-07-27 16:13: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.
Comment 1 thorsten.martens 2003-07-28 13:24:34 UTC 
TM->JA: As TZ mentioned, you might have a look. Thanks !
Comment 2 Joost Andrae 2003-07-29 15:49:11 UTC 
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.
Comment 3 hennes.rohling 2003-08-22 09:50:53 UTC 
Accepted.
Comment 4 dankegel 2003-08-22 10:47:50 UTC 
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.
Comment 5 Frank Schönheit 2003-10-28 07:06:20 UTC 
this is no crash, thus removing dependency to issue 21786
Comment 6 hennes.rohling 2003-11-24 15:14:00 UTC 
crash reporter is raised by abort() in OOo 1.1.0.
Comment 7 hennes.rohling 2003-11-26 09:52:04 UTC 
Closed.