From: Grant Edwards <grante@visi.com>
To: Kevin Buettner <kevinb@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: dump memory to file
Date: Wed, 22 Aug 2001 11:02:00 -0000 [thread overview]
Message-ID: <20010822130408.A32137@visi.com> (raw)
In-Reply-To: <1010822175224.ZM31365@ocotillo.lan>
On Wed, Aug 22, 2001 at 10:52:24AM -0700, Kevin Buettner wrote:
> > A while back I had asked if gdb could dump a section of target
> > memory to disk (as bin, elf, hex, whatever). The answer at the
> > time was no -- is that still the case? If I added such a
> > command, would it be of interest to anybody else? (IOW, should
> > I submit a patch?)
>
> 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. Maybe something along the
> following lines?
>
> (gdb) redirect-output /tmp/foo
> (gdb) x/10000x 0x01000
> (gdb) print/x $pc
> (gdb) x/100i $pc-200
> (gdb) redirect-output STDOUT
>
> And, it'd also be nice to redirect to be able to redirect to two or
> more destinations at the same time...
>
> (gdb) redirect-output /tmp/foo STDOUT
That would be really nice, particularly for printing large
structures (or arrays of structures) for archival or automated
analysis. But, I think the binary dump/restore function still
needs to be there:
1) I'd like to be able to dump data in a format understood by
objcopy. That way, you can convert it to specific formats
needed by other tools (e.g. RPOM programmer), link it into
another program, etc.
2) Redirecting output doesn't provide a way to load a chunk
from disk back to target memory. I don't need to do this
nearly as often, but it would occasionally be handy.
--
Grant Edwards
grante@visi.com
next prev parent reply other threads:[~2001-08-22 11:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-22 8:58 Grant Edwards
2001-08-22 10:18 ` Eli Zaretskii
2001-08-22 10:52 ` Kevin Buettner
2001-08-22 11:00 ` Daniel Jacobowitz
2001-08-22 12:00 ` Andrew Cagney
2001-08-22 11:02 ` Grant Edwards [this message]
2001-08-22 11:25 ` Per Bothner
2001-08-22 12:06 ` Kevin Buettner
2001-08-22 12:11 ` Andrew Cagney
2001-08-22 13:50 ` Jamie Guinan
2001-08-22 14:19 ` Grant Edwards
2001-08-22 10:25 Hiro Sugawara
2001-08-22 10:31 ` Grant Edwards
2001-08-22 10:43 ` Kevin Buettner
2001-08-22 10:51 ` Grant Edwards
2001-08-22 11:25 ` Kevin Buettner
2001-08-22 11:01 Hiro Sugawara
2001-08-22 11:10 ` Grant Edwards
2001-08-22 11:18 Hiro Sugawara
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=20010822130408.A32137@visi.com \
--to=grante@visi.com \
--cc=gdb@sources.redhat.com \
--cc=kevinb@cygnus.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