From: Michael Meissner <meissner@cygnus.com>
To: "Michael S. Miles" <mmiles@alacritech.com>
Cc: GDB Mailing List <gdb@sources.redhat.com>
Subject: Re: capture gdb output
Date: Thu, 19 Apr 2001 13:44:00 -0000 [thread overview]
Message-ID: <20010419164449.A21666@cse.cygnus.com> (raw)
In-Reply-To: <KIEKJCGPOOADIOGPDJJLGEBJDKAA.mmiles@alacritech.com>
On Thu, Apr 19, 2001 at 08:54:04AM -0400, Michael S. Miles wrote:
> 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.
>
> Does anyone know if gdb has this functionality and if so, how to use it?
>
> If it helps, I am using the 03/20/01 snapshot of GDB on a Linux-i386 system.
> I am also using it as a remote Linux kernel debugger although I don't
> believe that is relevant.
Besides using tee, you could run gdb within an emacs shell session (or use
emacs' gdb mode) and copy the buffer to a file, or use the 'script' command
that many Unixen provide (output is in the 'typescript' file). On older
systems, xterm might have a logging option (which was disabled due to security
concerns).
--
Michael Meissner, Red Hat, Inc. (GCC group)
PMB 198, 174 Littleton Road #3, Westford, Massachusetts 01886, USA
Work: meissner@redhat.com phone: +1 978-486-9304
Non-work: meissner@spectacle-pond.org fax: +1 978-692-4482
next prev parent reply other threads:[~2001-04-19 13:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2001-04-19 8:32 ` Unable to step through ARM code using insgiht-5.0 Keith Seitz
2001-04-19 6:04 capture gdb output Nicolas.Thery
2001-04-19 6:30 ` Michael S. Miles
2001-04-30 9:25 ` 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=20010419164449.A21666@cse.cygnus.com \
--to=meissner@cygnus.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