On Friday, October 08, 2010 10:39:14 am Michael Stahl wrote:
> hello Hugo,
> 
> On 08/10/2010 07:47, Hugo Pereira Da Costa wrote:
> > Hello,
> > Since a couple of weeks, open office crashes badly in kde and using
> > oxygen from trunk. It is apparently somewhere in the oxygen code. My
> > best guess is that open office passes some null pointer to the style and
> > I did not protect the code against it.
> > If this is the case that should be pretty easy to fix except that ...
> > ... I have no idea how to get a useable backtrace from the crash.
> > 
> > Only thing I get is this automatic recovery thingy popping up, but no
> > core dump, no debug output, nothing. Can someone give me (or point me
> > to) instructions to get any of the above ? Having none of these infos
> > makes debugging very difficult.
> 
> i think that is the expected behavior for end users :)
> 

I agree. Was asking on a dev POV :)


> well, the easiest would be to just attach gdb to the running soffice.bin
> process.
> this may run into trouble if OOo crashes at startup.
> for crashes during startup, you can try to run soffice.bin directly, or,
> in case that doesn't work for you, modify the "soffice" wrapper script to
> run gdb (near the bottom, at comment "execute soffice binary").
> 
> gdb should catch the signal (whatever it is) that is raised on crashing.
> if you can get OOo to use your KDE libraries built with debug information,
> then that should give you a hint where it crashes with the usual "bt"
> command.
> 
> or did i misunderstand you and your main problem is actually that you
> cannot reproduce the crash yourself?

No no you understood right. I can reproduce (quite accurately and 
systematically) the problem :)
Thanks for all the suggestions, I'll do that !
Hopefully we'll have this fixed soon ...

Hugo

> 
> > Thanks in advance,
> > 
> > Hugo
> > 
> > (Oxygen Developer)
> 
> regards,
>  michael

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@openoffice.org
For additional commands, e-mail: dev-h...@openoffice.org

Reply via email to