From: Eli Zaretskii <eliz@gnu.org>
To: Andrew Burgess <aburgess@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 2/2] gdb: add support for disassembler styling using libopcodes
Date: Fri, 17 Jun 2022 14:16:32 +0300 [thread overview]
Message-ID: <835ykzpmjz.fsf@gnu.org> (raw)
In-Reply-To: <eb9059907131fd9acb37ead1b4fc8aa9ff7a1e18.1655462053.git.aburgess@redhat.com> (message from Andrew Burgess via Gdb-patches on Fri, 17 Jun 2022 11:36:02 +0100)
> Date: Fri, 17 Jun 2022 11:36:02 +0100
> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
> Cc: Andrew Burgess <aburgess@redhat.com>
>
> gdb/NEWS | 28 +++++++
> gdb/cli/cli-style.c | 107 +++++++++++++++++++++++---
> gdb/cli/cli-style.h | 28 +++++--
> gdb/disasm.c | 184 ++++++++++++++++++++++++++++++++++++++++++--
> gdb/disasm.h | 16 ++++
> gdb/doc/gdb.texinfo | 100 +++++++++++++++++++++++-
> 6 files changed, 437 insertions(+), 26 deletions(-)
Thanks, the documentation parts are approved, with these minor nits:
> @@ -26485,13 +26486,30 @@
> general is enabled (with @code{set style enabled on}), and if a source
> highlighting library is available to @value{GDBN}.
>
> -To highlight disassembler output, @value{GDBN} must be compiled with
> -Python support, and the Python Pygments package must be available. If
> -these requirements are not met then @value{GDBN} will not highlight
> -disassembler output, even when this option is @samp{on}.
> +The two source highlighting libraries that @value{GDBN} could use are;
> +@value{GDBN}'s builtin disassembler, or the Python Pygments package.
The original text explicitly talked about styling disassembler output,
whereas the new text omits that qualification, and sounds as if it is
talking about styling in general. Although this is in a section about
disassembly, I'd prefer to keep the original qualification.
> +If neither of these options are available then @value{GDBN} will
> +produce unstyled output, even when this setting is @samp{on}.
Same here.
> +@item disassembler immediate
> +Control the styling of numeric operands in the disassembler output.
> +These are managed with the @code{set style disassembler immediate}
> +family of commands. This style is not used for instruction operands
> +that represent addresses, in that case the @samp{disassembler address}
> +style is used. This style is only used when @value{GDBN} is styling
^^
Two spaces between sentences.
> +@anchor{maint_libopcodes_styling}
> +@kindex maint set libopcodes-styling enabled
> +@kindex maint show libopcodes-styling enabled
> +@item maint set libopcodes-styling enabled @r{[}on|off@r{]}
> +@itemx maint show libopcodes-styling enabled
> +Control whether @value{GDBN} should use its builtin disassembler
> +(libopcodes) to style disassembler output (@pxref{Output Styling}).
^^^^^^^^^^
"libopcodes" should have the @file markup.
next prev parent reply other threads:[~2022-06-17 11:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:36 [PATCH 0/2] Use libopcodes disassembler styling with GDB Andrew Burgess
2022-06-17 10:36 ` [PATCH 1/2] gdb: have gdb_disassemble_info carry 'this' in its stream pointer Andrew Burgess
2022-06-17 10:36 ` [PATCH 2/2] gdb: add support for disassembler styling using libopcodes Andrew Burgess
2022-06-17 11:16 ` Eli Zaretskii [this message]
2022-06-30 12:22 ` Andrew Burgess
2022-06-30 13:46 ` Eli Zaretskii
2022-07-04 10:15 ` Andrew Burgess
2022-07-20 2:09 ` Simon Marchi
2022-07-20 13:14 ` [PATCH 0/2] Fix some undefined haviour bugs in Python disassembler API Andrew Burgess
2022-07-20 13:14 ` [PATCH 1/2] gdb: fix use of uninitialised gdb_printing_disassembler::m_in_comment Andrew Burgess
2022-07-20 14:21 ` Simon Marchi
2022-07-20 13:14 ` [PATCH 2/2] gdb/python: fix invalid use disassemble_info::stream Andrew Burgess
2022-07-25 18:27 ` [PATCH 0/2] Fix some undefined haviour bugs in Python disassembler API Andrew Burgess
2022-07-04 10:17 ` [PATCH 0/2] Use libopcodes disassembler styling with GDB Andrew Burgess
2022-07-11 14:18 ` 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=835ykzpmjz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=aburgess@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).