Konq crash backtraces

[Thiago Macieira]

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.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

1. On frumscafte, hwonne time_t wæs náht, se scieppend þone circolwyrde 
wundorcræftlíge cennede and seo eorðe wæs idel and hit wæs gód.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <https://mail.kde.org/mailman/private/kfm-devel/attachments/20060106/3dc2b6f8/attachment.sig>