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

List:       kde-devel
Subject:    Re: Computing software bts automatically
From:       Lubos Lunak <l.lunak () suse ! cz>
Date:       2006-04-29 8:40:35
Message-ID: 200604291040.35900.l.lunak () suse ! cz
[Download RAW message or body]

On Friday 28 April 2006 23:05, Paulo J. Matos wrote:
> On 28/04/06, Ivor Hewitt <ivor@ivor.org> wrote:
> > Paulo J. Matos wrote:
> > > Hi all,
> > >
> > > I'm quite curious on how KDE currently computes the backtraces of
> > > software when it crashes. Can someone explain me or point me to some
> > > references on this issue?
> >
> > It invokes gdb. Although I recently spent some time writing code to walk
> > the stack and collect symbol information, so I'd be happy to answer any
> > questions.
>
> It invokes gdb on what? The dumped core?
> Is there any gdb API for that invocation or KDE starts gdb as a
> separate process and goes through all the work of handling the
> communication between the processes?

 Crash-handling is done by the KCrash class (kdelibs/kdecore/kcrash.*) and the 
drkonqi binary (kdebase/drkonqi/). KCrash takes over when any problem is 
encountered, launched drkonqi with info about the app and blocks. Drkonqi 
invokes gdb on the blocked process and takes care of the rest.

-- 
Lubos Lunak
KDE developer
---------------------------------------------------------------------
SuSE CR, s.r.o.  e-mail: l.lunak@suse.cz , l.lunak@kde.org
Drahobejlova 27  tel: +420 2 9654 2373
190 00 Praha 9   fax: +420 2 9654 2374
Czech Republic   http://www.suse.cz/
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]