Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
Cc: gdb@sourceware.org
Subject: Re: possible gdb agent expression extension
Date: Sat, 23 Aug 2014 07:32:00 -0000	[thread overview]
Message-ID: <83fvgnmzk7.fsf@gnu.org> (raw)
In-Reply-To: <12648.1408745258@usendtaylorx2l>

> Date: Fri, 22 Aug 2014 18:07:38 -0400
> From: David Taylor <dtaylor@usendtaylorx2l.lss.emc.com>
> 
> Hopefully the markup is correct:

I cannot comment on the markup's idea because I don't really
understand what you are trying to say using that markup.  I think the
larger context is missing.

That @result{} at the end, with nothing after it, does look strange:
what "result" does this give?

> @item @code{setmem8} (0x??): @var{addr} @var{value} @result{}
> @item @code{setmem16} (0x??): @var{addr} @var{value} @result{}
> @item @code{setmem32} (0x??): @var{addr} @var{value} @result{}
> @item @code{setmem64} (0x??): @var{addr} @var{value} @result{}

If this is part of a @table, you will be much better off using "@table
@code", so that 0x?? etc. will be rendered in the appropriate
typeface.  (Btw, what does "0x??" signify?)

> Pop an address @var{addr} and a value @{value} from the stack.  For
> bytecode @code{setmem}@var{n}, set the @var{n}-bit value at @var{addr}
> to the least significant @var{n}-bits of @var{value}.  Ignoring
> architecture pointer alignment issues, it is as if the operation
> 
> *@code{uint}@var{n}@code{_t}@var{addr} = @code{uint}@var{n}@code{_t}@var{value}

You cannot stick a code portion in the middle of text just like that,
you should use @smallexample (and then drop the @code parts, as they
are automatically used for text inside @smallexample).


  reply	other threads:[~2014-08-23  7:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-28 14:39 David Taylor
2014-08-22 22:08 ` David Taylor
2014-08-23  7:32   ` Eli Zaretskii [this message]
2014-08-25 14:03     ` David Taylor
2014-08-25 15:06       ` Eli Zaretskii
2014-08-25 16:30         ` David Taylor
2014-08-25 16:44           ` Eli Zaretskii

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=83fvgnmzk7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dtaylor@usendtaylorx2l.lss.emc.com \
    --cc=gdb@sourceware.org \
    /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