https://bugs.freedesktop.org/show_bug.cgi?id=64962
--- Comment #5 from Stephan Bergmann <[email protected]> --- (In reply to comment #4) > I would -dearly- love to have these un-caught extensions caught and printed > out un-conditionally, in shipping builds at the top-level to help debug this > stuff; did we decide not to do that for some reason ? [ we do on Android > IIRC ]. Note that this is from a non-main thread, so generic catching of css::uno::Exception to print its Message would need to go into osl_thread_start_Impl, but that's too low-level to know css::uno::Exception. The best approach would be if css::uno::Exception inherited from std::exception and would use its what() for Message, so that GCC's __gnu_cxx::__verbose_terminate_handler would print it out along with the exception's type. But that would be an incompatible change. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
