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

List:       kde-core-devel
Subject:    Re: FW: KCrash API
From:       Waldo Bastian <bastian () suse ! de>
Date:       2000-04-14 17:01:16
[Download RAW message or body]

On Fri, 14 Apr 2000, Richard Moore wrote:
> > -----Original Message-----
> > From: Seehuber, Emmeran [mailto:E.Seehuber@Mylius.com]
> > Sent: Freitag, 14. April 2000 16:48
> > To: Hummel, Timo
> > Subject: KCrash API
> > 
> > Hi Timo,
> > 
> > i´m not subscriped to the kde-core-devel list, but i´ve ridden
> > your mail through the mailing list archive. You perhaps should also
> > catch this signals:
> > 
> > - SIGABRT (Normaly caused through assert()´s)
> 
> Not sure about this one - it is better to use NDEBUG to stop assertions
> (and best of all is to make sure they are not violated).
> 
> > - SIGFPE
> 
> Yep
> 
> > - SIGILL
> 
> ???? I assume this is SIGKILL. If so then we should not catch this.
> Unless we simply route it through to the exit action.

/usr/include/asm/signal.h:#define SIGILL                 4
/usr/include/asm/signal.h:#define SIGKILL                9                        

I guess SIGILL stands for "illegal inststruction". You can't catch
SIGKILL.

Cheers,
Waldo

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