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

[Jose' Matos]

On Tuesday 15 November 2005 08:49, 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.
I have followed the procedure you have described with gdb, after the crash 
the backtrace reveals: 
 
0x00c01402 in __kernel_vsyscall () 
(gdb) bt 
#0  0x00c01402 in __kernel_vsyscall () 
#1  0x0072f8e8 in sendmsg () from /lib/libc.so.6 
#2  0x00eec7ee in sys_sendmsg () from /lib/libdsocks.so.0 
#3  0x00efa9bf in Rsendmsg () from /lib/libdsocks.so.0 
#4  0x00efaaf7 in Rsend () from /lib/libdsocks.so.0 
#5  0x00efab57 in Rwrite () from /lib/libdsocks.so.0 
#6  0x00eed20b in write () from /lib/libdsocks.so.0 
#7  0x054b61de in XUnlockDisplay () from /usr/X11R6/lib/libX11.so.6 
#8  0x054b63fc in _X11TransWrite () from /usr/X11R6/lib/libX11.so.6 
#9  0x0549b79b in _XError () from /usr/X11R6/lib/libX11.so.6 
#10 0x0549b8b6 in _XReply () from /usr/X11R6/lib/libX11.so.6 
#11 0x05497ac1 in XTranslateCoordinates () from /usr/X11R6/lib/libX11.so.6 
#12 0x00f3b3e7 in X11SalFrame::HandleSizeEvent () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#13 0x00f3df8d in X11SalFrame::Dispatch () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#14 0x00f65784 in SalX11Display::Dispatch () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#15 0x00f65a39 in SalX11Display::Yield () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#16 0x00f601d6 in SalDisplay::BestVisual () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#17 0x00f5fbcd in SalData::XIOErrorHdl () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#18 0x00f5f75d in SalXLib::Yield () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#19 0x00f66afa in X11SalInstance::Yield () 
from /usr/lib/openoffice.org2.0/program/libvclplug_gen680li.so 
#20 0x03da7594 in Application::Yield () 
from /usr/lib/openoffice.org2.0/program/libvcl680li.so 
#21 0x03da75ca in Application::Execute () 
from /usr/lib/openoffice.org2.0/program/libvcl680li.so 
#22 0x005d1c73 in desktop::Desktop::Main () 
from /usr/lib/openoffice.org2.0/program/libsoffice.so 
#23 0x03dac99f in InitVCL () 
from /usr/lib/openoffice.org2.0/program/libvcl680li.so 
#24 0x03daca4f in SVMain () 
from /usr/lib/openoffice.org2.0/program/libvcl680li.so 
#25 0x005ccad7 in sal_main () 
from /usr/lib/openoffice.org2.0/program/libsoffice.so 
#26 0x005ccb23 in main () 
from /usr/lib/openoffice.org2.0/program/libsoffice.so 
#27 0x00678d5f in __libc_start_main () from /lib/libc.so.6 
#28 0x080484c5 in _start () 
 
Yes, I have dante running here and it shows in the first calls.
This happened before, so I don't think that dante is the culprit here.

I am running kde without klipper running, at least dcop does not say so. Is 
there any distinct trace that I should be looking into?

I did not modified any of $LANG* or $LC_* so they have the default value.

> Attaching such crashreports to
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=171873 would be
> appreciated.

  I have done so.

> C.

-- 
José Abílio