Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index


On 19/11/10 17:39, Michael Meeks wrote:

On Fri, 2010-11-19 at 16:33 +0000, Andrew wrote:
I might have a go if you can give me some way to invoke the crash report
detector - so I can see what it looks like.

      We need more crashes ! [ "there's an app for that" ;-]. You could (I
guess) try killing soffice.bin thusly:

      pkill -11 -f soffice.bin

      (simulating a SEGV) - really we should have some regression tests that
do this sort of thing as well - to test the crash recovery code.

      HTH,

              Michael.


Hmm, that crashed LibreOffice, and then when I started it again, the
Document Recovery Tool opened. At the last step, where it says 'Click
next to open the Error Reporting Tool', I clicked next, but the error
reporting tool didn't open and it just went to Writer.

I am using the latest build from the LibO website - how can I access the
error reporting tool?

-- 
Andrew

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.