From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PING (docs)] Re: [PATCH] [1/2] Add new 'z' format for print command
Date: Wed, 24 Jul 2013 14:35:00 -0000 [thread overview]
Message-ID: <83k3kgvxf2.fsf@gnu.org> (raw)
In-Reply-To: <51EFA750.2070707@broadcom.com>
> Date: Wed, 24 Jul 2013 11:07:12 +0100
> From: "Andrew Burgess" <aburgess@broadcom.com>
> cc: "Eli Zaretskii" <eliz@gnu.org>
>
> I just need a docs review on the change below please.
Sorry for missing it.
> gdb/NEWS
>
> * New 'z' formatter for print and examine memory commands, displays the
> value as hexadecimal zero padded to the size of the type.
The comma before "displays" should be removed. Also, "for printing
and examining", rather than "print and examine".
More importantly, I have a difficulty understanding what does
"hexadecimal zero padded to the size ..." mean. More accurately, if
my interpretation of what you say (that 'z' produces "00"s for
non-existing data, then why does this "padding" make sense, when we
are targeting a human consumer?
Thanks.
next prev parent reply other threads:[~2013-07-24 14:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 17:30 Andrew Burgess
2013-07-10 17:30 ` Tom Tromey
2013-07-11 15:20 ` Andrew Burgess
2013-07-18 7:57 ` Andrew Burgess
2013-07-24 10:07 ` [PING (docs)] " Andrew Burgess
2013-07-24 14:35 ` Eli Zaretskii [this message]
2013-07-24 15:16 ` Andrew Burgess
2013-07-24 17:00 ` Eli Zaretskii
2013-07-24 17:08 ` Andrew Burgess
2013-07-24 17:43 ` Eli Zaretskii
2013-07-25 10:18 ` Andrew Burgess
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=83k3kgvxf2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@broadcom.com \
--cc=gdb-patches@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