On 23 May 2016 at 12:57, Stephan Bergmann <sbergman@redhat.com> wrote:
The crash handling code called from within the signal handler is just a
big mess of illegal activity (that apparently happens to work some of the
time, but is also known to fail spectacularly sometimes). Locking the
SolarMutex is just one of many illegal aspects. I wouldn't worry trying to
take care of it independently of cleaning up the big mess completely.
Would it not be easier (and safer) to create some small, independent
programs, that use no other parts of LibreOffice, and wrap the main
executable, and catch all and any exceptions and then do whatever we need
to do: upload a dump, set some of kind "attempt restore" flag in the
registry, etc, etc.
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.