OpenOffice.org2 regularly crashing without warning and no option for feedback.

[Robin Laing]

Caolan McNamara wrote:
> On Tue, 2005-11-15 at 15:35 +1100, Rodd Clarkson wrote:
> 
>>Hi All,
>>
>>My wife uses OpenOffice.org (on an FC4 laptop that is up-to-date with
>>udpates) as her main applications and recently (in the last week) she's
>>been having problems where OOo just 'disappears' (her words) and offers
>>no chance for feedback about what was happening.
>>
>>She's loosing 15 minute chunks of work and this is happening a couple of
>>times a day.
>>
>>I'm on FC-rawhide and don't use OOo enough to have this problem.
>>
>>Are others seeing this too?  How can I get some useful backtrace to
>>report what the problem is?  gdb maybe?
> 
> 
> I've gotten reports of this on FC-4, but have not been able to reproduce
> it, I need a real stack trace. One problem is that the auto-stack trace
> provider on FC-4 doesn't kick in for a trivial and fixed in rawhide
> reason so I'm not getting the stack-traces on crash.
> 
> So to debug...
> 
> 
>>gdb /usr/lib/openoffice.org/program/soffice.bin
> 
> (gdb) handle SIG33 nostop noprint
> (gdb) handle SIGPWR nostop noprint
> (gdb) handle SIGXCPU nostop noprint
> (gdb) run -writer
> 
> and on crash
> 
> (gdb) bt.
> 
> Attaching such crashreports to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171873
> would be appreciated.
> 

Hello, I am trying this as I am having this problem and I want to get 
it resolved.  When I try the above method for running gdb (which I 
have no clue about) I get an error on the "run" line.

(gdb) run -writer
Starting program:  -writer
No executable file specified.
Use the "file" or "exec-file" command.


I found that the first line has to be gdb 
/usr/lib/openoffice.org2.0/program/soffice.bin

Just in case someone else that is new to this, I thought I would pass 
it on.

Robin