From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@broadcom.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] MI disassemble opcode support
Date: Wed, 15 Dec 2010 18:17:00 -0000 [thread overview]
Message-ID: <83lj3qhpey.fsf@gnu.org> (raw)
In-Reply-To: <4D08C355.9010809@broadcom.com>
> Date: Wed, 15 Dec 2010 13:32:05 +0000
> From: "Andrew Burgess" <aburgess@broadcom.com>
>
> Provide an equivalent to "disassemble /r" for the MI interface. The mode parameter to -data-disassemble is extended to control opcode dumping.
Thanks.
> I've updated the docs in gdb/doc/gdb.texinfo but I didn't know what I was supposed to do to update the gdb/doc/gdb.info-4 file
Nothing. gdb.info-* files are produced from gdb.texinfo when GDB is
built.
> 2010-12-10 Andrew Burgess <aburgess@broadcom.com>
>
> * gdb.texinfo: Update to reflect changes in mi/mi-cmd-disas.c
The ChangeLog entry should show the name of the node where this change
was made (as if the node were a function).
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -27567,8 +27567,9 @@ displayed; if @var{lines} is higher than the number of lines between
> @var{start-addr} and @var{end-addr}, only the lines up to @var{end-addr}
> are displayed.
> @item @var{mode}
> -is either 0 (meaning only disassembly) or 1 (meaning mixed source and
> -disassembly).
> +is either 0 (meaning only disassembly), 1 (meaning mixed source and
> +disassembly), 2 (meaning disassembly with raw opcodes), or 3 (meaning
> +mixed source and disassembly with raw opcodes).
> @end table
This part is okay.
> + MODE: 0 -- disassembly.
> + 1 -- disassembly and source.
> + 2 -- disassembly and opcodes.
> + 3 -- disassembly and source and opcodes.
Please edit the last line to be valid English:
3 -- disassembly, source and opcodes.
The patch for the manual is okay with these changes.
next prev parent reply other threads:[~2010-12-15 18:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-15 13:32 Andrew Burgess
2010-12-15 18:17 ` Eli Zaretskii [this message]
2010-12-16 10:46 ` Andrew Burgess
2010-12-28 6:35 ` Joel Brobecker
2010-12-28 19:12 ` Eli Zaretskii
2011-01-04 11:35 ` Andrew Burgess
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=83lj3qhpey.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@broadcom.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