[lug] OT: Dumping gdb backtrace data to a file?

[D. Stimits]

D. Stimits wrote:

> Scott Herod wrote:
>
> > Hello,
> >
> > A quick gdb question:  Is it possible to dump the results of a gdb
> > command to a file?  I'm trying debug a massively multi-threaded app.
> > which, not surprisingly, seems to have a problem with thread-death.  The
> > results of "thread apply all bt" goes on for hundreds of lines. Is there
> > some way to dump all of that to a file so I can diff. multiple crashes?
> >
> > Thanks,
> >
> > Scott
>
>
>
> Haven't tried, but some interactive apps you can redirect via use of
> "tee". Just pipe both stdin and stdout to "tee filename.txt". In some
> cases it interferes with data entry, but in many it works.


Brain burp...stdout and stderr, not stdin. Just read my post. No need to 
redirect stdin...plus it would be guaranteed to fail then. Just pipe to 
tee, try it and see if it logs while allowing you to interact.

D. Stimits, stimits AT attbi.com

>
> D. Stimits, stimits AT attbi.com
>
> _______________________________________________
> Web Page:  http://lug.boulder.co.us
> Mailing List: http://lists.lug.boulder.co.us/mailman/listinfo/lug
> Join us on IRC: lug.boulder.co.us port=6667 channel=#colug
>