[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: kded crashes
From:       Steffen Hansen <stefh () mip ! sdu ! dk>
Date:       1999-07-12 18:20:25
[Download RAW message or body]

On Mon, 12 Jul 1999, Michael Reiher wrote:

> > To me it looks like kded crashed, but the IOR property was still
> > published. So Konqy tried to contact a non-existing kded.
> > 
> > Removing the property and restarting kded should fix it, or?
> Ahh, one has to no that:) Works now.

It seems that SIGABRT isn't catchable (I thought is was). Often kded
crashes are caused by a failed assert(bla); the result is that the X atom
stays after kded is died.

How do we solve this problem? Not using assert() isn't a fix. The problem
remains with other uncatchable signals (SIGKILL etc.)

greetings,
-- 
Steffen Hansen                            
email: stefh@mip.sdu.dk, stefh@imada.sdu.dk, hansen@kde.org 
URL:   http://www.mip.sdu.dk/~stefh       

[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic