From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 1726) id C4CD8385354C; Wed, 29 Jun 2022 12:54:45 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org C4CD8385354C Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable From: Andrew Burgess To: gdb-cvs@sourceware.org Subject: [binutils-gdb] gdb/doc: improve description of --data-disassemble opcodes output X-Act-Checkin: binutils-gdb X-Git-Author: Andrew Burgess X-Git-Refname: refs/heads/master X-Git-Oldrev: 69b46464badb01340a88d0ee57cdef0b7fdf545e X-Git-Newrev: 6c0fe6d8f963eee3da16bf4895b1c592596240ff Message-Id: <20220629125445.C4CD8385354C@sourceware.org> Date: Wed, 29 Jun 2022 12:54:45 +0000 (GMT) X-BeenThere: gdb-cvs@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-cvs mailing list List-Unsubscribe: , List-Archive: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2022 12:54:45 -0000 https://sourceware.org/git/gitweb.cgi?p=3Dbinutils-gdb.git;h=3D6c0fe6d8f963= eee3da16bf4895b1c592596240ff commit 6c0fe6d8f963eee3da16bf4895b1c592596240ff Author: Andrew Burgess Date: Wed Jun 22 11:39:00 2022 +0100 gdb/doc: improve description of --data-disassemble opcodes output =20 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 @sam= p{func-name}. The text disassembly for this @samp{address}. =20 @item opcodes -This field is only present for modes 2, 3 and 5. This contains the raw op= code -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. =20 @end table