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

List:       kde-devel
Subject:    Re: drkonqui - better trace command?
From:       David Faure <faure () kde ! org>
Date:       2007-03-26 14:09:45
Message-ID: 200703261609.46112.faure () kde ! org
[Download RAW message or body]

On Saturday 24 March 2007, Konrad Rosenbaum wrote:
> Hi,
> 
> while doing some research into debugging I noticed that drkonqui only traces 
> the current (ie. the crashed) thread, while other threads might also 
> contain important information.
> 
> I just tried to give drkonqui a more complete GDB script:
> --gdbrc--
> BacktraceCommand=thread\nthread apply all bt
> ----
> It seems to work.
> 
> thread -> will output the current thread ID (ie. the one that crashed)
> thread apply -> executes the command (bt) on the threads specified (all)

Good idea.

-- 
David Faure, faure@kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]