From: Luis Machado <lgustavo@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH v2 0/3] varobj zero-padded hexadecimal format
Date: Thu, 07 May 2015 17:37:00 -0000 [thread overview]
Message-ID: <1431020207-14371-1-git-send-email-lgustavo@codesourcery.com> (raw)
This is v2 of the set of patches to add support for the zero-padded hexadecimal
format for varobj's, defined as "zero-hexadecimal". We currently only support
regular non-zero-padded hexadecimal.
Talking with IDE developers, they would like to have this option that is
already available to GDB's print/x commands in the CLI as 'z'.
v2 adds a bit more documentation regarding the new format and
also changes its identifier from 'zhexadecimal' to 'zero-hexadecimal'
Luis Machado (3):
Add zero-padded hexadecimal format support for varobj's
Add varobj zero-hexadecimal format tests.
Documentation changes for the new zero-hexadecimal format
gdb/NEWS | 6 ++++++
gdb/doc/gdb.texinfo | 7 ++++++-
gdb/mi/mi-cmd-var.c | 4 +++-
gdb/testsuite/gdb.mi/mi-var-display.exp | 25 +++++++++++++++++++++++--
gdb/varobj.c | 5 +++--
gdb/varobj.h | 3 ++-
6 files changed, 43 insertions(+), 7 deletions(-)
--
1.9.1
next 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 Luis Machado [this message]
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 ` [PATCH v2 3/3] Documentation changes for the new zero-hexadecimal format Luis Machado
2015-05-07 18:01 ` 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-1-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).