Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Ulrich Weigand" <uweigand@de.ibm.com>
Cc: gdb-patches@sourceware.org, drow@false.org
Subject: Re: [rfc/rfa] [3/4] SPU enhancements: gdbserver support
Date: Sun, 03 Jun 2007 16:44:00 -0000	[thread overview]
Message-ID: <E1HutBM-0007Wx-1X@fencepost.gnu.org> (raw)
In-Reply-To: <200706031328.l53DSIYF001704@d12av02.megacenter.de.ibm.com> 	(uweigand@de.ibm.com)

> Date: Sun, 3 Jun 2007 15:28:18 +0200 (CEST)
> From: "Ulrich Weigand" <uweigand@de.ibm.com>
> Cc: gdb-patches@sourceware.org, drow@false.org
> 
> > > +Write @var{length} bytes of uninterpreted data into the target's
> > > +special data area identified by the keyword @var{object}, starting
> > 
> > What do you mean by ``keyword''?  Isn't @var{object} a _name_ of an
> > object or its symbol?
> 
> This is just copied from the pre-existing text (also present in the
> qXfer::read section).  In any case, I think "keyword" is right here,
> as you can only use one of the defined strings ("auxv", "memory-map",
> "spu", ...) as "object".

Then please say something like this:

  (@var{object} can be @samp{auxv}, @samp{memory-map}, @samp{spu}...)

> Is the following version OK?

Yes, but please add the above.

Thanks.


  reply	other threads:[~2007-06-03 16:44 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-02 19:33 Ulrich Weigand
2007-06-02 20:33 ` Eli Zaretskii
2007-06-03 13:28   ` Ulrich Weigand
2007-06-03 16:44     ` Eli Zaretskii [this message]
2007-06-04 13:58       ` Ulrich Weigand
2007-06-04 19:19         ` Eli Zaretskii
2007-06-04 20:02           ` Ulrich Weigand
2007-06-04 19:54 ` Daniel Jacobowitz
2007-06-04 20:05   ` Ulrich Weigand
2007-06-04 20:10     ` Daniel Jacobowitz
2007-06-05 18:34       ` Daniel Jacobowitz
2007-06-05 23:02         ` Ulrich Weigand
2007-06-06 17:51           ` Eli Zaretskii
2007-06-12 13:58           ` Daniel Jacobowitz
2007-06-12 14:43             ` Ulrich Weigand

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=E1HutBM-0007Wx-1X@fencepost.gnu.org \
    --to=eliz@gnu.org \
    --cc=drow@false.org \
    --cc=gdb-patches@sourceware.org \
    --cc=uweigand@de.ibm.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