Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: fam@euphon.net
To: gdb-patches@sourceware.org
Cc: fam@euphon.net, Andreas Schwab <schwab@linux-m68k.org>,
	Simon Marchi <simark@simark.ca>
Subject: [PATCH v6 0/3] disass: Add /x modifier
Date: Sat, 26 Sep 2020 08:35:36 +0100	[thread overview]
Message-ID: <20200926073539.981936-1-fam@euphon.net> (raw)

From: Fam Zheng <famzheng@amazon.com>

v6: Add texinfo section name in ChangeLog. [Eli]

v5: Add function names in ChangeLog. [Eli]

v4: Add ChangeLog entries. [Eli]

v3: Add a test, more doc, and drop tmp buffer. [Andreas, Simon, Pedro]

This is a new modifier for disass command, to print offsets in hex. This
reduces pain for low level debugging (Linux kernel, Xen, etc.) when the
backtraces from dmesg are in hex - no manual converting needed to do a cross
matching when looking at both sides at the same time.

Fam Zheng (3):
  disass: Add /x modifier to print offsets in hex
  disass: Add test for /x mode
  disass: Add texinfo doc for the /x modifier

 gdb/NEWS                                |  3 ++
 gdb/cli/cli-cmds.c                      | 17 +++++++----
 gdb/disasm.c                            |  5 +++-
 gdb/disasm.h                            |  1 +
 gdb/doc/gdb.texinfo                     | 38 +++++++++++++++++++------
 gdb/record.c                            |  3 ++
 gdb/testsuite/gdb.base/disasm-optim.exp |  7 +++++
 7 files changed, 59 insertions(+), 15 deletions(-)

-- 
2.25.1



             reply	other threads:[~2020-09-26  7:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26  7:35 fam [this message]
2020-09-26  7:35 ` [PATCH v6 1/3] disass: Add /x modifier to print offsets in hex fam
2020-09-26  7:35 ` [PATCH v6 2/3] disass: Add test for /x mode fam
2020-09-26  7:35 ` [PATCH v6 3/3] disass: Add texinfo doc for the /x modifier fam
2020-09-26  8:18   ` Eli Zaretskii via Gdb-patches
2020-09-26  8:49     ` Fam Zheng

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=20200926073539.981936-1-fam@euphon.net \
    --to=fam@euphon.net \
    --cc=gdb-patches@sourceware.org \
    --cc=schwab@linux-m68k.org \
    --cc=simark@simark.ca \
    /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