Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Craig Blackmore <craig.blackmore@embecosm.com>
Cc: gdb-patches@sourceware.org, aburgess@redhat.com
Subject: Re: [PATCH v5 1/1] gdb: Add python support for transforming register unwind values
Date: Mon, 08 Jun 2026 15:13:05 +0300	[thread overview]
Message-ID: <86cxy1jkmm.fsf@gnu.org> (raw)
In-Reply-To: <20260608120437.566738-2-craig.blackmore@embecosm.com> (message from Craig Blackmore on Mon, 8 Jun 2026 13:04:37 +0100)

> From: Craig Blackmore <craig.blackmore@embecosm.com>
> Cc: aburgess@redhat.com,
> 	eliz@gnu.org,
> 	Craig Blackmore <craig.blackmore@embecosm.com>
> Date: Mon,  8 Jun 2026 13:04:37 +0100
> 
> This patch addresses the scenario where a register value is saved in
> some mangled form on the target and gdb does not have sufficient
> information to demangle it.
> 
> After getting a register value from an unwinder, gdb will call out to
> extension languages to allow the value to be transformed.  This avoids
> having to write a new unwinder and allows the standard unwinders to be
> used.
> 
> This patch adds the python class
> `gdb.unwinder.UnwindRegisterValueTransformer` which is the base class
> for transformers which provide a `read` method for transforming unwind
> register values that have been read.  There is no similar support for
> transforming values being written back to the target as this was not
> something I needed to be able to do.  Such support can be added to the
> python API in future by supporting a `write` method.  Currently writing
> back to a transformed register will produce an "Attempt to assign to an
> unmodifiable value" error.
> 
> Only one transformer can be registered globally at any one time.
> Attempting to register more than one transformer or to any other locus
> produces an error.  The function for registering transformers takes a
> locus to allow other loci to be supported in future.  Registered
> transformers are stored in a list so that registering multiple
> transformers may be supported in future.
> 
> `gdbpy_get_register_descriptor` is now externally visible as it is used
> to create a gdb.RegisterDescriptor object to pass to the `read` method.
> 
> This patch adds read-only attribute `gdb.Value.lval_type` which
> transformer methods can use to decide to skip modifying values that did
> not come directly from the target and may not need transforming, for
> example, values taken directly from DWARF.
> ---
>  gdb/NEWS                                      |  17 ++
>  gdb/doc/python.texi                           |  96 ++++++++++
>  gdb/extension-priv.h                          |   8 +
>  gdb/extension.c                               |  35 ++++
>  gdb/extension.h                               |   6 +
>  gdb/frame.c                                   |  10 ++
>  gdb/guile/guile.c                             |   2 +
>  gdb/python/lib/gdb/__init__.py                |  21 +++
>  gdb/python/lib/gdb/unwinder.py                |  93 +++++++++-
>  gdb/python/py-registers.c                     |   2 +-
>  gdb/python/py-unwind.c                        | 169 ++++++++++++++++++
>  gdb/python/py-value.c                         |  21 +++
>  gdb/python/python-internal.h                  |   3 +
>  gdb/python/python.c                           |   4 +-
>  .../gdb.python/py-unwind-transformer-error.py |  33 ++++
>  .../gdb.python/py-unwind-transformer.c        |  80 +++++++++
>  .../gdb.python/py-unwind-transformer.exp      | 115 ++++++++++++
>  .../gdb.python/py-unwind-transformer.py       |  48 +++++
>  gdb/testsuite/gdb.python/py-value.exp         |   8 +
>  19 files changed, 768 insertions(+), 3 deletions(-)
>  create mode 100644 gdb/testsuite/gdb.python/py-unwind-transformer-error.py
>  create mode 100644 gdb/testsuite/gdb.python/py-unwind-transformer.c
>  create mode 100644 gdb/testsuite/gdb.python/py-unwind-transformer.exp
>  create mode 100644 gdb/testsuite/gdb.python/py-unwind-transformer.py

Thanks, the documentation parts are okay.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2026-06-08 12:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-10 11:04 [RFC PATCH] gdb: Add python support for demangling " Craig Blackmore
2025-04-10 12:31 ` Eli Zaretskii
2025-05-08 10:17 ` [RFC PATCH v2] " Craig Blackmore
2025-05-08 11:40   ` Eli Zaretskii
2025-05-12 13:15   ` Andrew Burgess
2026-04-30 15:19     ` Craig Blackmore
2026-04-30 15:31     ` [PATCH v3] " Craig Blackmore
2026-04-30 16:05       ` Eli Zaretskii
2026-05-20 13:16       ` [PATCH v4 0/1] " Craig Blackmore
2026-05-20 13:16         ` [PATCH v4 1/1] " Craig Blackmore
2026-05-20 15:44           ` Eli Zaretskii
2026-05-21  9:47           ` Andrew Burgess
2026-05-27 10:49             ` Craig Blackmore
2026-06-08 12:04         ` [PATCH v5 0/1] " Craig Blackmore
2026-06-08 12:04           ` [PATCH v5 1/1] gdb: Add python support for transforming " Craig Blackmore
2026-06-08 12:13             ` Eli Zaretskii [this message]
2026-07-15  9:56           ` [PING][PATCH v5 0/1] gdb: Add python support for demangling " Craig Blackmore
2026-07-29 15:01           ` [PATCH " Craig Blackmore

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=86cxy1jkmm.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=aburgess@redhat.com \
    --cc=craig.blackmore@embecosm.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