From: Andrew Burgess <andrew.burgess@embecosm.com>
To: gdb-patches@sourceware.org
Subject: [PATCH 0/5] Python Unwinders and Inline Frames
Date: Wed, 17 Jun 2020 18:38:04 +0100 [thread overview]
Message-ID: <cover.1592415321.git.andrew.burgess@embecosm.com> (raw)
I ran into an issue with Python frame unwinders and inline frames.
The fix for which is in patch #5 of this series.
In order to write a test for patch #5 I needed some extra
functionality from the Python API, which resulted in patches #2 - #4.
And while writing patch #2 I noticed the cleanup that's in patch #1.
Feedback welcome,
Thanks,
Andrew
---
Andrew Burgess (5):
gdb: Remove deprecated_set_gdbarch_data
gdb/python: Add architecture method to gdb.PendingFrame
gdb/python: Add gdb.Architecture.registers method
gdb/python: New method to access list of register groups
gdb: Fix Python unwinders and inline frames
gdb/ChangeLog | 61 +++
gdb/Makefile.in | 1 +
gdb/NEWS | 10 +
gdb/doc/ChangeLog | 21 +
gdb/doc/gdb.texinfo | 1 +
gdb/doc/python.texi | 70 +++
gdb/findvar.c | 28 +-
gdb/gdbarch.c | 22 +-
gdb/gdbarch.h | 3 -
gdb/gdbarch.sh | 25 +-
gdb/ia64-libunwind-tdep.c | 15 +-
gdb/python/py-arch.c | 45 ++
gdb/python/py-registers.c | 464 ++++++++++++++++++
gdb/python/py-unwind.c | 20 +
gdb/python/python-internal.h | 6 +
gdb/python/python.c | 1 +
gdb/testsuite/ChangeLog | 19 +
.../gdb.python/py-arch-reg-groups.exp | 87 ++++
.../gdb.python/py-arch-reg-names.exp | 87 ++++
gdb/testsuite/gdb.python/py-unwind-inline.c | 37 ++
gdb/testsuite/gdb.python/py-unwind-inline.exp | 49 ++
gdb/testsuite/gdb.python/py-unwind-inline.py | 71 +++
gdb/testsuite/gdb.python/py-unwind.py | 10 +-
gdb/user-regs.c | 18 +-
24 files changed, 1097 insertions(+), 74 deletions(-)
create mode 100644 gdb/python/py-registers.c
create mode 100644 gdb/testsuite/gdb.python/py-arch-reg-groups.exp
create mode 100644 gdb/testsuite/gdb.python/py-arch-reg-names.exp
create mode 100644 gdb/testsuite/gdb.python/py-unwind-inline.c
create mode 100644 gdb/testsuite/gdb.python/py-unwind-inline.exp
create mode 100644 gdb/testsuite/gdb.python/py-unwind-inline.py
--
2.25.4
next reply other threads:[~2020-06-17 17:38 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-17 17:38 Andrew Burgess [this message]
2020-06-17 17:38 ` [PATCH 1/5] gdb: Remove deprecated_set_gdbarch_data Andrew Burgess
2020-06-18 21:11 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 2/5] gdb/python: Add architecture method to gdb.PendingFrame Andrew Burgess
2020-06-17 18:20 ` Eli Zaretskii
2020-06-18 21:18 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 3/5] gdb/python: Add gdb.Architecture.registers method Andrew Burgess
2020-06-17 18:25 ` Eli Zaretskii
2020-06-18 21:24 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 4/5] gdb/python: New method to access list of register groups Andrew Burgess
2020-06-17 18:27 ` Eli Zaretskii
2020-06-17 18:40 ` Christian Biesinger
2020-06-18 8:44 ` Andrew Burgess
2020-06-18 21:27 ` Tom Tromey
2020-06-17 17:38 ` [PATCH 5/5] gdb: Fix Python unwinders and inline frames Andrew Burgess
2020-06-17 21:14 ` Luis Machado
2020-06-18 8:25 ` Andrew Burgess
2020-06-18 10:29 ` Luis Machado
2020-06-18 17:42 ` Andrew Burgess
2020-06-18 21:35 ` Tom Tromey
2020-06-22 15:47 ` Andrew Burgess
2020-06-23 14:16 ` Luis Machado
2020-07-02 21:07 ` Andrew Burgess
2020-07-06 17:43 ` 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.1592415321.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