Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Grant Edwards <grante@visi.com>
To: Orjan Friberg <orjan.friberg@axis.com>
Cc: Paul Dubuc <pdubuc@cas.org>, gdb@sourceware.cygnus.com
Subject: Re: Redirect GDB command output?
Date: Fri, 05 Oct 2001 08:47:00 -0000	[thread overview]
Message-ID: <20011005105018.A1405@visi.com> (raw)
In-Reply-To: <3BBDCDD9.6E281600@axis.com>

On Fri, Oct 05, 2001 at 05:12:25PM +0200, Orjan Friberg wrote:
> Grant Edwards wrote:
> > 
> > On Wed, Oct 03, 2001 at 03:02:19PM -0400, Paul Dubuc wrote:
> > 
> > > Is there any way to redirect GDB command output to a file (either
> > > interactively or in user-defined commands)?
> > 
> > Nope.  People (like me) have been asking about that for a long
> > time, but none of have actually done anything about it.  :)
> 
> Maybe I'm stating the obvious here, or maybe this is not the
> feature you guys were looking for, but you can use tee like
> this: 'gdb | tee log 2>&1', and all gdb output will be put in
> the file 'log' (in addition to appearing on stdout of course).

The problem is that I often don't know that I want to save the
output of a command when I start gdb.  Once I've managed to
induce the failure, it's too late.  I suppose I could always
log gdb output in case I might want to save something, but that
seems like a clumsy solution.

-- 
Grant Edwards
grante@visi.com


  reply	other threads:[~2001-10-05  8:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-03 12:02 Paul Dubuc
2001-10-05  7:23 ` Grant Edwards
2001-10-05  8:12   ` Orjan Friberg
2001-10-05  8:47     ` Grant Edwards [this message]
2001-10-05  9:34     ` Paul Dubuc
2001-10-05 11:27       ` Tom Tromey
2001-10-05 11:44         ` Paul Dubuc
2001-10-09 21:56           ` Andrew Cagney

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=20011005105018.A1405@visi.com \
    --to=grante@visi.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=orjan.friberg@axis.com \
    --cc=pdubuc@cas.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