From: Andrew Cagney <ac131313@cygnus.com>
To: "Michael S. Miles" <mmiles@alacritech.com>
Cc: Nicolas.Thery@Symbian.com,
GDB Mailing List <gdb@sources.redhat.com>,
gdb-owner@sources.redhat.com
Subject: Re: capture gdb output
Date: Mon, 30 Apr 2001 09:25:00 -0000 [thread overview]
Message-ID: <3AED91ED.8C7CE28A@cygnus.com> (raw)
In-Reply-To: <KIEKJCGPOOADIOGPDJJLCEBNDKAA.mmiles@alacritech.com>
"Michael S. Miles" wrote:
>
> Nicolas,
>
> > > I need to be able to capture all the output from my gdb session
> > into some
> > > type of log file. It seems like this is a feature that would definitely
> > > exist, but I have been searching the sources and documentation for any
> > > mention of this capability with no luck.
> >
>
> > Isn't sufficient to use "gdb ... 2>&1 | tee log.txt" ?
>
> I just tried this and it works great! My colleagues and I thank you so
> much!
>
> I would still be interested in whether there is a function in gdb to open or
> close a log file during a session?
It is certainly listed in the TODO file:
--
Add a transcript mechanism to GDB.
Such a mechanism might log all gdb input and output to a file in a
form that would allow it to be replayed. It could involve ``gdb
--transcript=FILE'' or it could involve ``(gdb) transcript file''.
--
Andrew
next prev parent reply other threads:[~2001-04-30 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 6:04 Nicolas.Thery
2001-04-19 6:30 ` Michael S. Miles
2001-04-30 9:25 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 2:57 Unable to step through ARM code using insgiht-5.0 Ahmed A. Agbabiaka
2001-04-19 5:53 ` capture gdb output Michael S. Miles
2001-04-19 13:44 ` Michael Meissner
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=3AED91ED.8C7CE28A@cygnus.com \
--to=ac131313@cygnus.com \
--cc=Nicolas.Thery@Symbian.com \
--cc=gdb-owner@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=mmiles@alacritech.com \
/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