This is the mail archive of the
gdb-prs@sources.redhat.com
mailing list for the GDB project.
gdb/198: redirect output using (gdb) >>FILE <command>
- To: gdb-gnats at sources dot redhat dot com
- Subject: gdb/198: redirect output using (gdb) >>FILE <command>
- From: ac131313 at cygnus dot com
- Date: 22 Aug 2001 19:19:40 -0000
- Cc: per at bothner dot com
- Reply-To: ac131313 at cygnus dot com
>Number: 198
>Category: gdb
>Synopsis: redirect output using (gdb) >>FILE <command>
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible: unassigned
>State: open
>Class: change-request
>Submitter-Id: net
>Arrival-Date: Wed Aug 22 12:28:00 PDT 2001
>Closed-Date:
>Last-Modified:
>Originator: per@bothner.com
>Release: unknown-1.0
>Organization:
>Environment:
N/A
>Description:
Per Bothner writes:
Kevin Buettner <kevinb@cygnus.com> writes:
> I think it'd be nice to provide a more general solution. I.e, I think
> it'd be nice if GDB had a facility whereby output from subsequent
> commands would be redirected to a file.
It might be nice to have a stateless option. For example using a
variant of the standard shell syntax for appending to a file:
(gdb) >>FILENAME COMMAND
For example:
(gdb) >>/tmp/foo x/10000x 0x01000
Though it is also useful for it to span mutliple commands. One could
so that if there is no command:
(gdb) >>FILENAME
--
Cagney writes:
It does have an effect on the syntax. The commands:
(gdb) >>FILE print 1+ 2
(gdb) print 1 + 2 >>FILE
are very different
--
See also gdb/128
>How-To-Repeat:
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted: