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

List:       kde-core-devel
Subject:    Re: KCrash API
From:       David Faure <david () mandrakesoft ! com>
Date:       2000-04-14 13:09:10
[Download RAW message or body]

On Fri, Apr 14, 2000 at 02:43:48PM +0100, Richard Moore wrote:
> 
> 
> David Faure wrote:
> > 
> > On Thu, Apr 13, 2000 at 01:28:30PM +0100, Richard Moore wrote:
> > >
> > >
> > > "Hummel, Timo" wrote:
> > >
> > > > If you want everything being handled automatically, you don't need to do
> > > > anything, since everything is made in the KApplication class. The default
> > > > behaviour is: Catch SIGSEGV, launch Dr. Konqi and display the informations.
> > > > If there are other suitable signals which should be handled, please tell me.
> > >
> > > I need to catch SIGPIPE in kpsion, is that handled already or not?
> > 
> > I catch SIGPIPE for kioslave and job
> >   (i.e. any app using something from kio/job.h...)
> > But as opposed to SIGSEGV, the application is happy to go on after a SIGPIPE,
> > so I prefer that it gets ignored, rather than if DrKonqi popped up.
> > There is already the "slave kio_xyz died" message box.
> > 
> > I guess this doesn't prevent KCrash from handling SIGPIPE, but it
> > should not conflict with that...
> 
> Sure, I just ignore it too. I just wanted to know if KCrash already
> did it.

It doesn't currently.

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/
KDE, Making The Future of Computing Available Today

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