public inbox for gdb-cvs@sourceware.org
help / color / mirror / Atom feed
From: Andrew Burgess <aburgess@sourceware.org>
To: gdb-cvs@sourceware.org
Subject: [binutils-gdb] gdb/doc: improve description of --data-disassemble opcodes output
Date: Wed, 29 Jun 2022 12:54:45 +0000 (GMT)	[thread overview]
Message-ID: <20220629125445.C4CD8385354C@sourceware.org> (raw)

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=6c0fe6d8f963eee3da16bf4895b1c592596240ff

commit 6c0fe6d8f963eee3da16bf4895b1c592596240ff
Author: Andrew Burgess <aburgess@redhat.com>
Date:   Wed Jun 22 11:39:00 2022 +0100

    gdb/doc: improve description of --data-disassemble opcodes output
    
    Extend the description of the MI command --data-disassemble.
    Specifically, expand the description of the 'opcodes' field to explain
    how the bytes are formatted.

Diff:
---
 gdb/doc/gdb.texinfo | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/gdb/doc/gdb.texinfo b/gdb/doc/gdb.texinfo
index 38ae249f62d..5dbae6d0106 100644
--- a/gdb/doc/gdb.texinfo
+++ b/gdb/doc/gdb.texinfo
@@ -34454,8 +34454,10 @@ The decimal offset in bytes from the start of @samp{func-name}.
 The text disassembly for this @samp{address}.
 
 @item opcodes
-This field is only present for modes 2, 3 and 5.  This contains the raw opcode
-bytes for the @samp{inst} field.
+This field is only present for modes 2, 3 and 5.  This contains the
+raw opcode bytes for the @samp{inst} field.  The bytes are formatted
+as single bytes, in hex, in ascending address order, with a single
+space between each byte.
 
 @end table


                 reply	other threads:[~2022-06-29 12:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220629125445.C4CD8385354C@sourceware.org \
    --to=aburgess@sourceware.org \
    --cc=gdb-cvs@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).