Computing software bts automatically

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?

Thanks,
--
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 <<

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.

Cheers,

-- 
Ivor
http://www.ivor.it
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

On 28/04/06, Ivor Hewitt <ivorivor.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?

Thanks,

Paulo Matos

> Cheers,
>
> --
> Ivor
> http://www.ivor.it
>


--
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 <<

On Friday 28 April 2006 16:05, Paulo J. Matos wrote:
> On 28/04/06, Ivor Hewitt <ivorivor.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.
--
Matt
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

On Friday 28 April 2006 23:05, Paulo J. Matos wrote:
> On 28/04/06, Ivor Hewitt <ivorivor.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.lunaksuse.cz , l.lunakkde.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 <<

On 29/04/06, Matt Rogers <mattrkde.org> wrote:
> On Friday 28 April 2006 16:05, Paulo J. Matos wrote:
> > On 28/04/06, Ivor Hewitt <ivorivor.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 <<

On 29/04/06, Lubos Lunak <l.lunaksuse.cz> wrote:
> On Friday 28 April 2006 23:05, Paulo J. Matos wrote:
> > On 28/04/06, Ivor Hewitt <ivorivor.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.
>

OK, I'll take a look into those classes. Thanks...

> --
> Lubos Lunak
> KDE developer
>
------------------------------------------------------------
---------
> SuSE CR, s.r.o.  e-mail: l.lunaksuse.cz , l.lunakkde.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 <<
>


--
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 <<

So could we add a button to drkonqi labelled 'debug in
gdb'  which
launches a terminal with gdb running and attached?

On 4/29/06, Paulo J. Matos <pocmatosgmail.com> wrote:
> On 29/04/06, Lubos Lunak <l.lunaksuse.cz> wrote:
> > On Friday 28 April 2006 23:05, Paulo J. Matos
wrote:
> > > On 28/04/06, Ivor Hewitt <ivorivor.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.
> >
>
> OK, I'll take a look into those classes. Thanks...
>
> > --
> > Lubos Lunak
> > KDE developer
> >
------------------------------------------------------------
---------
> > SuSE CR, s.r.o.  e-mail: l.lunaksuse.cz ,
l.lunakkde.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 <<
> >
>
>
> --
> 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
> <<
>
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<

On Sunday 30 April 2006 09:40, John Tapsell wrote:
> So could we add a button to drkonqi labelled 'debug in
gdb'  which
> launches a terminal with gdb running and attached?

in $KDEHOME/share/config/drkonqi:

[drkonqi]
ConfigName=developer

Cheers,
Hamish.
 
>> Visit 
http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
unsubscribe <<