Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/2] Allow gdb.RegisterDescriptors to be used in read_register calls
Date: Fri, 24 Jul 2020 10:57:50 +0100	[thread overview]
Message-ID: <cover.1595584512.git.andrew.burgess@embecosm.com> (raw)

Now that we have Python RegisterDescriptor objects available we can
improve an ugly dependency on GDBs internal register numbering that is
currently exposed in the Python API.  See patch #2 for more details.

Thanks,
Andrew

---

Andrew Burgess (2):
  gdb: Add a find method for RegisterDescriptorIterator
  gdb/python: make more use of RegisterDescriptors

 gdb/ChangeLog                                 | 24 +++++
 gdb/doc/ChangeLog                             | 11 +++
 gdb/doc/python.texi                           | 50 +++++++---
 gdb/python/py-frame.c                         | 22 +++--
 gdb/python/py-registers.c                     | 92 ++++++++++++++++++-
 gdb/python/py-unwind.c                        | 36 +-------
 gdb/python/python-internal.h                  | 19 ++++
 gdb/testsuite/ChangeLog                       |  9 ++
 .../gdb.python/py-arch-reg-names.exp          | 15 +++
 gdb/testsuite/gdb.python/py-unwind.py         | 11 ++-
 10 files changed, 231 insertions(+), 58 deletions(-)

-- 
2.25.4



             reply	other threads:[~2020-07-24  9:57 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-24  9:57 Andrew Burgess [this message]
2020-07-24  9:57 ` [PATCH 1/2] gdb: Add a find method for RegisterDescriptorIterator Andrew Burgess
2020-07-24 10:32   ` Eli Zaretskii
2020-07-24 23:17     ` Andrew Burgess
2020-07-25  6:27       ` Eli Zaretskii
2020-07-24 18:22   ` Tom Tromey
2020-07-24  9:57 ` [PATCH 2/2] gdb/python: make more use of RegisterDescriptors Andrew Burgess
2020-07-24 10:36   ` Eli Zaretskii
2020-07-24 18:38   ` 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=cover.1595584512.git.andrew.burgess@embecosm.com \
    --to=andrew.burgess@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