From: Eli Zaretskii via Gdb-patches <gdb-patches@sourceware.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/9] gdb/doc: improve description of --data-disassemble opcodes output
Date: Thu, 23 Jun 2022 19:09:47 +0300 [thread overview]
Message-ID: <838rpne4z8.fsf@gnu.org> (raw)
In-Reply-To: <10e9e1a8e94b17fb96f7c944c77d729aceb8fc19.1655999715.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Thu, 23 Jun 2022 17:05:08 +0100)
> Date: Thu, 23 Jun 2022 17:05:08 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Andrew Burgess <aburgess@redhat.com>
>
> Extend the description of the MI command --data-disassemble.
> Specifically, expand the description of the 'opcodes' field to explain
> how the bytes are formatted.
> ---
> gdb/doc/gdb.texinfo | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
Thanks, this is OK.
next prev parent reply other threads:[~2022-06-23 16:12 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-23 16:05 [PATCH 0/9] Disassembler opcode display and text alignment Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 1/9] gdb/doc: improve description of --data-disassemble opcodes output Andrew Burgess via Gdb-patches
2022-06-23 16:09 ` Eli Zaretskii via Gdb-patches [this message]
2022-06-29 12:54 ` Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 2/9] gdb/testsuite: new test for -data-disassemble opcodes format Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 3/9] gdb/disasm: read opcodes bytes with a single read_code call Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 4/9] gdb: disassembler opcode display formatting Andrew Burgess via Gdb-patches
2022-06-23 16:14 ` Eli Zaretskii via Gdb-patches
2022-06-23 16:05 ` [PATCH 5/9] gdb: make gdb_disassembly_flag unsigned Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 6/9] gdb/doc: fix column widths in MI compatibility table Andrew Burgess via Gdb-patches
2022-06-23 16:22 ` Eli Zaretskii via Gdb-patches
2022-06-30 9:39 ` Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 7/9] gdb/doc: update syntax of -data-disassemble command arguments Andrew Burgess via Gdb-patches
2022-06-23 16:21 ` Eli Zaretskii via Gdb-patches
2022-06-30 10:18 ` Andrew Burgess via Gdb-patches
2022-06-30 10:46 ` Eli Zaretskii via Gdb-patches
2022-06-23 16:05 ` [PATCH 8/9] gdb/mi: some int to bool conversion Andrew Burgess via Gdb-patches
2022-06-23 16:05 ` [PATCH 9/9] gdb/mi: new options for -data-disassemble command Andrew Burgess via Gdb-patches
2022-06-23 16:34 ` Eli Zaretskii via Gdb-patches
2022-06-30 11:22 ` Andrew Burgess via Gdb-patches
2022-06-30 13:36 ` Eli Zaretskii via Gdb-patches
2022-07-25 18:28 ` [PATCH 0/9] Disassembler opcode display and text alignment Andrew Burgess via Gdb-patches
2022-09-05 14:11 ` Andrew Burgess via Gdb-patches
2022-09-21 16:41 ` Tom Tromey
2022-10-02 13:15 ` Andrew Burgess via Gdb-patches
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=838rpne4z8.fsf@gnu.org \
--to=gdb-patches@sourceware.org \
--cc=aburgess@redhat.com \
--cc=eliz@gnu.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