Issue 94351 - pass information about uncaught/unexpected C++ exceptions to crash reporting
Summary: pass information about uncaught/unexpected C++ exceptions to crash reporting
Status: ACCEPTED
Alias: None
Product: porting
Classification: Code
Component: code (show other issues)
Version: DEV300m31
Hardware: All All
: P3 Trivial (vote)
Target Milestone: 4.x
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-09-26 09:11 UTC by Stephan Bergmann
Modified: 2017-05-20 11:33 UTC (History)
3 users (show)

See Also:
Issue Type: ENHANCEMENT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description Stephan Bergmann 2008-09-26 09:11:43 UTC
There are often crash reports where the crash is caused by
std::terminate/std::unexpected due to an uncaught/unexpected C++ exception
(e.g., issue 94226 and issue 94240), where information about the exception
(exact type, message string) could help in diagnosing the cause of the crash. 
However, such information (that would be available in the terminate/unexpected
handler) is currently not present in the generated crash report data.
Comment 1 Stephan Bergmann 2008-09-26 09:12:11 UTC
.
Comment 2 Stephan Bergmann 2009-01-16 09:53:12 UTC
cannot remember why I stated that exception information "would be available in
the terminte/unexpected handler"
Comment 3 mikhail.voytenko 2009-02-26 11:50:25 UTC
Adding the file name and line number in any exception ( could be done
automatically ) would allow to identify the throwing statement uniquely. I had
already cases, when the same exception was thrown from the same method more than
once, and the crash report has shown the throwing statement wrongly.

The benefit of line information adding is that it does not cost performance at
all, it happens during the compilation time. 
Comment 4 Marcus 2017-05-20 11:33:28 UTC
Reset assigne to the default "issues@openoffice.apache.org".