This is the mail archive of the
mailing list for the GDB project.
Re: export backtrace
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.
On Jun 25, 2007, at 11:14 AM, Dan Kegel wrote:
On 6/25/07, Bram Kuijper <firstname.lastname@example.org> 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