From: Eli Zaretskii <eliz@is.elta.co.il>
To: Michael Snyder <msnyder@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] New commands, dump/restore memory<-->file
Date: Tue, 26 Mar 2002 22:50:00 -0000 [thread overview]
Message-ID: <Pine.SUN.3.91.1020327084845.5838L-100000@is> (raw)
In-Reply-To: <200203270146.g2R1kKL15221@reddwarf.cygnus.com>
On Tue, 26 Mar 2002, Michael Snyder wrote:
> Back in January, there was a discussion about adding commands that
> would allow gdb to copy data from target memory to a file and back
> again. Andrew and I have done an implementation of those commands,
> and here it is for your approval.
Thanks.
I find it disturbing, to say the least, that more and more new commands
come without documentation. Please consider adding some minimal docs.
TIA
next prev parent reply other threads:[~2002-03-27 6:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-26 17:57 Michael Snyder
2002-03-26 22:50 ` Eli Zaretskii [this message]
2002-03-27 8:29 ` Andrew Cagney
2002-03-27 13:31 ` Michael Snyder
2002-03-27 13:45 ` Andrew Cagney
2002-03-27 17:09 ` Michael Snyder
2002-03-27 17:49 ` Andrew Cagney
2002-03-28 1:24 ` Eli Zaretskii
2002-03-28 1:15 ` Eli Zaretskii
2002-03-28 17:24 ` Michael Snyder
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=Pine.SUN.3.91.1020327084845.5838L-100000@is \
--to=eliz@is.elta.co.il \
--cc=gdb-patches@sources.redhat.com \
--cc=msnyder@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