Apache OpenOffice (AOO) Bugzilla – Issue 94351
pass information about uncaught/unexpected C++ exceptions to crash reporting
Last modified: 2017-05-20 11:33:28 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.
.
cannot remember why I stated that exception information "would be available in the terminte/unexpected handler"
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.
Reset assigne to the default "issues@openoffice.apache.org".