From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCH 0/2] Use libopcodes disassembler styling with GDB
Date: Fri, 17 Jun 2022 11:36:00 +0100 [thread overview]
Message-ID: <cover.1655462053.git.aburgess@redhat.com> (raw)
libopcodes is slowly gaining the ability to provide styling
information for its disassembler output.
This series extends GDB to make use of this information where possible
(currently only i386 based architectures and RISC-V).
---
Andrew Burgess (2):
gdb: have gdb_disassemble_info carry 'this' in its stream pointer
gdb: add support for disassembler styling using libopcodes
gdb/NEWS | 28 ++++++
gdb/cli/cli-style.c | 107 ++++++++++++++++++++--
gdb/cli/cli-style.h | 28 ++++--
gdb/disasm.c | 217 +++++++++++++++++++++++++++++++++++++++++---
gdb/disasm.h | 81 ++++++++++++-----
gdb/doc/gdb.texinfo | 100 +++++++++++++++++++-
6 files changed, 503 insertions(+), 58 deletions(-)
--
2.25.4
next reply other threads:[~2022-06-17 10:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 10:36 Andrew Burgess [this message]
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
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=cover.1655462053.git.aburgess@redhat.com \
--to=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).