https://bugs.freedesktop.org/show_bug.cgi?id=58177
Michael Stahl <mst...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |UNCONFIRMED
Resolution|NOTOURBUG |---
CC| |mst...@redhat.com,
| |sberg...@redhat.com
--- Comment #7 from Michael Stahl <mst...@redhat.com> ---
there are actually several possibilities:
1) Duden code throws the exception and it is not allowed to pass though
Duden::ContextMenuInterceptor::notifyContextMenuExecute(com::sun::star::ui::ContextMenuExecuteEvent
const&)
2) the implementation of this method has a wrong exception specification:
Duden::ContextMenuInterceptor::notifyContextMenuExecute(com::sun::star::ui::ContextMenuExecuteEvent
const&)
3) the Duden code calls some LibreOffice API, which throws an exception that it
is allowed to throw
4) the Duden code calls some LibreOffice API, which throws an exception that it
is not allowed to throw (i.e. that is not listed in the exception specification
of the API)
1) 2) 3) would be bugs in the Duden code, while 4) would be a bug in
LibreOffice code
in case of 4) it would still crash in this way because LibreOffice is compiled
with -fno-enforce-eh-specs.
somebody with a Mac should do an --enable-dbgutil build (which does not use
-fno-enforce-eh-specs) and then try to reproduce the problem; if you get the
same stack then one of 1) 2) 3) is happening, while if you get terminate
directly in LO code then it is 4)
also, sberg is of the opinion that option b) in comment #4 is not a solution
but only a workaround
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
