unhandled exception / abort etc. ...
sbergman at redhat.com
Wed Feb 29 08:00:57 PST 2012
On 02/29/2012 03:29 PM, Michael Meeks wrote:
> So - it took me a while to get around to this, but luckily while I was
> I hit this. Interestingly on Linux we do get some (not particularly
> helpful) console debug:
> $ ./soffice /tmp/foo.odp
> terminate called after throwing an instance of
> And of course, no auto-save, no contents of the exception etc. etc. And
> I imagine the same is true for all un-caught exceptions, including
> (incidentally ::std::bad_alloc() ;-). I imagine that at the moment
> actively discards document data left& right in the vast majority of
> cases where it is not caught.
Strange. At least for my (--enable-dbgutil) master build, following the
instructions of fdo#46340 *does* lead to a restart with crash dialog and
Also, experimenting with the attached crash.patch (see also
<https://issues.apache.org/ooo/show_bug.cgi?id=108411> "let SID_CRASH
really crash") does lead to the crash dialog in all four variations of
the code (std::abort() vs. throw std::bad_alloc() and directly from main
thread vs. pthread_create).
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1852 bytes
Desc: not available
More information about the LibreOffice