From: Luis Machado <lgustavo@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH v2 3/3] Documentation changes for the new zero-hexadecimal format
Date: Thu, 07 May 2015 17:37:00 -0000 [thread overview]
Message-ID: <1431020207-14371-4-git-send-email-lgustavo@codesourcery.com> (raw)
In-Reply-To: <1431020207-14371-1-git-send-email-lgustavo@codesourcery.com>
This patch updates the documentation to reflect the addition of the new
zero-hexadecimal format option for -var-set-format and also adds a NEWS entry
for the change.
I changed it from zhexadecimal to zero-hexadecimal so the IDE folks can
properly translate the string to something more reasonable.
gdb/ChangeLog:
2015-05-07 Luis Machado <lgustavo@codesourcery.com>
* NEWS: Add new note to MI changes.
gdb/doc/ChangeLog:
2015-05-07 Luis Machado <lgustavo@codesourcery.com>
* gdb.texinfo (GDB/MI Variable Objects): Update text for
-var-set-format.
---
gdb/NEWS | 6 ++++++
gdb/doc/gdb.texinfo | 7 ++++++-
2 files changed, 12 insertions(+), 1 deletion(-)
diff --git a/gdb/NEWS b/gdb/NEWS
index 0c7084a..69a8f19 100644
--- a/gdb/NEWS
+++ b/gdb/NEWS
@@ -145,6 +145,12 @@ qXfer:exec-file:read
HP/PA running HP-UX hppa*-*-hpux*
Itanium running HP-UX ia64-*-hpux*
+* MI changes
+
+ ** The -var-set-format command now accepts the zero-hexadecimal
+ format. It outputs data in hexadecimal format with zero-padding on the
+ left.
+
*** Changes in GDB 7.9
* GDB now supports hardware watchpoints on x86 GNU Hurd.
diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 19d8bb3..ef0be3c 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -28927,13 +28927,18 @@ The syntax for the @var{format-spec} is as follows:
@smallexample
@var{format-spec} @expansion{}
- @{binary | decimal | hexadecimal | octal | natural@}
+ @{binary | decimal | hexadecimal | octal | natural | zero-hexadecimal@}
@end smallexample
The natural format is the default format choosen automatically
based on the variable type (like decimal for an @code{int}, hex
for pointers, etc.).
+The zero-hexadecimal format has a representation similar to hexadecimal
+but with padding zeroes to the left of the value. For example, a 32-bit
+hexadecimal value of 0x1234 would be represented as 0x00001234 in the
+zero-hexadecimal format.
+
For a variable with children, the format is set only on the
variable itself, and the children are not affected.
--
1.9.1
next prev parent reply other threads:[~2015-05-07 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-07 17:37 [PATCH v2 0/3] varobj zero-padded hexadecimal format Luis Machado
2015-05-07 17:37 ` [PATCH v2 2/3] Add varobj zero-hexadecimal format tests Luis Machado
2015-05-08 17:30 ` Joel Brobecker
2015-05-07 17:37 ` [PATCH v2 1/3] Add zero-padded hexadecimal format support for varobj's Luis Machado
2015-05-08 17:28 ` Joel Brobecker
2015-05-08 18:23 ` Luis Machado
2015-05-11 20:55 ` Joel Brobecker
2015-05-20 12:16 ` Luis Machado
2015-05-25 23:39 ` Luis Machado
2015-05-07 17:37 ` Luis Machado [this message]
2015-05-07 18:01 ` [PATCH v2 3/3] Documentation changes for the new zero-hexadecimal format 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=1431020207-14371-4-git-send-email-lgustavo@codesourcery.com \
--to=lgustavo@codesourcery.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).