public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Add pretty-printer base class and new methods
Date: Mon, 11 Sep 2023 11:28:24 -0600	[thread overview]
Message-ID: <20230911-pp-v2-v1-0-c4e0d40c8b63@adacore.com> (raw)

This adds a pretty-printer base class, to make it possible for gdb to
extend the pretty-printer API over time.

Then, a couple of new methods are added and the no-op array printer is
changed to use these, rather than the current approach of adding an
attribute and hoping it works ok.

Regression tested on x86-64 Fedora 36.

---
Tom Tromey (2):
      Introduce gdb.ValuePrinter
      Add two new pretty-printer methods

 gdb/NEWS                                      |  5 ++
 gdb/doc/python.texi                           | 68 ++++++++++++++++++++-------
 gdb/python/lib/gdb/dap/varref.py              | 22 ++++++---
 gdb/python/lib/gdb/printer/bound_registers.py |  9 ++--
 gdb/python/lib/gdb/printing.py                | 49 ++++++++++---------
 gdb/python/py-prettyprint.c                   | 65 +++++++++++++++++++++++++
 6 files changed, 168 insertions(+), 50 deletions(-)
---
base-commit: 14432bde076fdee66e6163993eadf592742935da
change-id: 20230911-pp-v2-9efa40abcc4e

Best regards,
-- 
Tom Tromey <tromey@adacore.com>


             reply	other threads:[~2023-09-11 17:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-11 17:28 Tom Tromey [this message]
2023-09-11 17:28 ` [PATCH 1/2] Introduce gdb.ValuePrinter Tom Tromey
2023-09-11 19:04   ` Eli Zaretskii
2023-09-26 14:08     ` Tom Tromey
2023-09-11 17:28 ` [PATCH 2/2] Add two new pretty-printer methods Tom Tromey
2023-09-11 19:00   ` Eli Zaretskii
2023-09-26 14:09 ` [PATCH 0/2] Add pretty-printer base class and new methods Tom Tromey

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=20230911-pp-v2-v1-0-c4e0d40c8b63@adacore.com \
    --to=tromey@adacore.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).