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

List:       kde-devel
Subject:    Re: Computing software bts automatically
From:       "Paulo J. Matos" <pocmatos () gmail ! com>
Date:       2006-04-29 11:17:42
Message-ID: 11b141710604290417o4fae274fw6bc872645803d047 () mail ! gmail ! com
[Download RAW message or body]

On 29/04/06, Matt Rogers <mattr@kde.org> wrote:
> On Friday 28 April 2006 16: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?
> >
>
> KDE starts gdb with --pid parameter for the application so that gdb can attach
> to the application.

How come he is able to get the pid of the process?? Once the process
crashes the pid disappears... or KDE started gdb as soon as the
process starts?

> --
> Matt
>


--
Paulo Jorge Matos - pocm at sat inesc-id pt
Web: http://sat.inesc-id.pt/~pocm
Computer and Software Engineering
INESC-ID - SAT Group
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]