From: Jim Ingham <jingham@apple.com>
To: Dan Kegel <dank@kegel.com>
Cc: Bram Kuijper <a.l.w.kuijper@rug.nl>, gdb@sourceware.org
Subject: Re: export backtrace
Date: Mon, 25 Jun 2007 19:19:00 -0000 [thread overview]
Message-ID: <BDB44984-0A10-4EE0-8DAC-753F3C267378@apple.com> (raw)
In-Reply-To: <a71bd89a0706251114u28fb2b9dg81865070ce51a0ce@mail.gmail.com>
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".
prev parent reply other threads:[~2007-06-25 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 15:07 Bram Kuijper
2007-06-25 15:09 ` Bob Rossi
2007-06-25 15:15 ` Andreas Schwab
2007-06-25 18:14 ` Dan Kegel
2007-06-25 19:19 ` Jim Ingham [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BDB44984-0A10-4EE0-8DAC-753F3C267378@apple.com \
--to=jingham@apple.com \
--cc=a.l.w.kuijper@rug.nl \
--cc=dank@kegel.com \
--cc=gdb@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox