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

List:       kde-core-devel
Subject:    Re: FW: KCrash API
From:       Richard Moore <rich () ipso-facto ! freeserve ! co ! uk>
Date:       2000-04-14 15:17:06
[Download RAW message or body]



"Hummel, Timo" wrote:
> 
> This is an idea from Emmeran Seehuber for catching additional signals.
> Feel free to discuss :)
> 
> Yours
> Timo
> 
> -----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.

Rich.

> 
> cu,
>   Emmy

-- 
     Richard Moore		rich@ipso-facto.freeserve.co.uk
http://www.robocast.com/	richard@robocast.com
http://developer.kde.org/	rich@kde.org

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