incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joost Andrae <Joost.And...@gmx.de>
Subject Re: How to enable crash log for AOO3.4?
Date Tue, 29 May 2012 13:39:00 GMT
Hi,

hmmm...

If the crash reporter within your Linux AOO build has crashdump enabled 
then just

kill -SEGV the PID of the soffice.bin process

and have a look at the stack trace that is shown within the ErrorReport 
dialog and compare it with the stack trace within RedHat's Bugzilla. The 
difference makes the basic symbol data that is shown within the call 
stack. This makes the call stack more readable for a developer who needs 
to debug the application. Within Sun's ReportMail backend we were able 
to map the call stack data into code pointers with line numbers.

> I was thinking of something similar to what ABRT does on Fedora:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=708361
>
> That bug was submitted by the ABRT tool, it only prompts for the
> bugzilla user and password, plus the description of what you where doing
> when the error occurred. IMHO, the automatic bug submittion is useful
> besides the usefulness of the stack trace.

Kind regards, Joost


Mime
View raw message