Konq crash backtraces

[Lubos Lunak]

Dne pátek 06 leden 2006 22:31 Thiago Macieira napsal(a):
> Dik Takken wrote:
> >It just happened again...
> >
> >Konqueror crashed without leaving a single trace. I compiled KDE 3.5
> > with full debug info, which gives me useful backtraces when a crash
> > occurs. Konqueror is a weird exception. One of its windows can just
> > disappear in front of your nose, without DrKonqi popping up to get a
> > backtrace.
> >
> >I do not use Konq preloading or shared instances, in order to avoid
> >difficulties like this.
> >
> >Can anyone point out why this happens? I just want to catch every crash
> > I can...
>
> Can you check if anything was logged to ~/.xsession-errors or similar
> output venue?
>
> Distributions are shipping glibc with some malloc checks, which cause it
> to abort the program when a double-free or corruption occurs, but without
> raising SIGABRT. There must be a way of making glibc raise the signal,
> but I don't know how. It should be enabled by default in KDE code so that
> the crash handler can catch them.

 Not really. The error checking does raise SIGABRT, it's just that our crash 
handler depends on malloc() working and locks up already in 
DCOPClient::emergencyClose(). If we want to get a crash handler for heap 
corruptions too, we need to stay away from using the corrupted malloc. I can 
give it a shot.

 As for the actual crash in this case, check whether you don't have qt-copy 
patch #0066 enabled, the crash looks very much like it.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak at suse.cz , l.lunak at kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/