export backtrace

export backtrace

[Bram Kuijper]

Hi all,
A veeeery simple question with an unfindable answer: how do I export a 
backtrace to a file so that I can search through it outside gdb?

(gdb) backtrace ./program > my_file obviously isn't working, so what 
should be the alternative?

thanks,
Bram

Re: export backtrace

[Bob Rossi]

On Mon, Jun 25, 2007 at 05:07:29PM +0200, Bram Kuijper wrote:
> Hi all,
> A veeeery simple question with an unfindable answer: how do I export a 
> backtrace to a file so that I can search through it outside gdb?
> 
> (gdb) backtrace ./program > my_file obviously isn't working, so what 
> should be the alternative?

One alternative would be to use the logging feature of gdb. That will
log the entire session, and will include the backtrace.

Bob Rossi

Re: export backtrace

[Andreas Schwab]

Bob Rossi <bob_rossi@cox.net> writes:

> On Mon, Jun 25, 2007 at 05:07:29PM +0200, Bram Kuijper wrote:
>> Hi all,
>> A veeeery simple question with an unfindable answer: how do I export a 
>> backtrace to a file so that I can search through it outside gdb?
>> 
>> (gdb) backtrace ./program > my_file obviously isn't working, so what 
>> should be the alternative?
>
> One alternative would be to use the logging feature of gdb. That will
> log the entire session, and will include the backtrace.

Or use Emacs as a frontend.

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Re: export backtrace

[Dan Kegel]

On 6/25/07, Bram Kuijper <a.l.w.kuijper@rug.nl> wrote:
> (gdb) backtrace ./program > my_file

Another workaround: run it in a window, then copy and paste.  Yuckky, but works.

But y'know, that would be a nice feature, so I filed a feature request
with summary "Please allow redirection of individual command output to files".

Re: export backtrace

[Jim Ingham]

Just define pre & post hooks for the command, and turn logging on in  
the pre hook, and off in the post hook.  Or define you own "logged"  
version of the command and stash that in your .gdbinit file.

Jim

On Jun 25, 2007, at 11:14 AM, Dan Kegel wrote:

> On 6/25/07, Bram Kuijper <a.l.w.kuijper@rug.nl> wrote:
>> (gdb) backtrace ./program > my_file
>
> Another workaround: run it in a window, then copy and paste.   
> Yuckky, but works.
>
> But y'know, that would be a nice feature, so I filed a feature request
> with summary "Please allow redirection of individual command output  
> to files".