From: Andrew Burgess <aburgess@redhat.com>
To: gdb-patches@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: [PATCHv2 0/3] Core file Python API
Date: Tue, 23 Sep 2025 14:44:05 +0100 [thread overview]
Message-ID: <cover.1758634958.git.aburgess@redhat.com> (raw)
In-Reply-To: <cover.1756828929.git.aburgess@redhat.com>
In v2:
+ Patches 1 and 3 updated inline with Tom's feedback.
+ Rebased to current HEAD.
+ Retested.
This series extends the Python API to allow users to query the
currently loaded core file, and to find out things about the core
file.
There's probably more features we could offer, but I think this is a
reasonable starting point.
All feedback welcome.
Thanks,
Andrew
---
Andrew Burgess (3):
gdb/python: introduce gdb.Corefile API
gdb: make structured core file mappings processing global
gdb/python: add Corefile.mapped_files method
gdb/Makefile.in | 1 +
gdb/NEWS | 33 ++
gdb/corelow.c | 225 ++++----
gdb/doc/python.texi | 110 ++++
gdb/gdbcore.h | 43 ++
gdb/observable.c | 1 +
gdb/observable.h | 6 +
gdb/python/py-corefile.c | 688 +++++++++++++++++++++++
gdb/python/py-inferior.c | 18 +
gdb/python/python-internal.h | 8 +
gdb/testsuite/gdb.python/py-corefile.c | 25 +
gdb/testsuite/gdb.python/py-corefile.exp | 236 ++++++++
gdb/testsuite/gdb.python/py-corefile.py | 144 +++++
13 files changed, 1437 insertions(+), 101 deletions(-)
create mode 100644 gdb/python/py-corefile.c
create mode 100644 gdb/testsuite/gdb.python/py-corefile.c
create mode 100644 gdb/testsuite/gdb.python/py-corefile.exp
create mode 100644 gdb/testsuite/gdb.python/py-corefile.py
base-commit: 84dd63f3279dc0d1e13351dbc7b11261800e4758
--
2.47.1
next prev parent reply other threads:[~2025-09-23 13:47 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 16:03 [PATCH " Andrew Burgess
2025-09-02 16:03 ` [PATCH 1/3] gdb/python: introduce gdb.Corefile API Andrew Burgess
2025-09-02 16:26 ` Eli Zaretskii
2025-09-16 17:25 ` Tom Tromey
2025-09-23 13:50 ` Andrew Burgess
2025-09-02 16:03 ` [PATCH 2/3] gdb: make structured core file mappings processing global Andrew Burgess
2025-09-16 17:28 ` Tom Tromey
2025-09-02 16:03 ` [PATCH 3/3] gdb/python: add Corefile.mapped_files method Andrew Burgess
2025-09-16 17:54 ` Tom Tromey
2025-09-23 13:52 ` Andrew Burgess
2025-09-23 13:44 ` Andrew Burgess [this message]
2025-09-23 13:44 ` [PATCHv2 1/3] gdb/python: introduce gdb.Corefile API Andrew Burgess
2025-10-03 18:56 ` Tom Tromey
2025-10-06 8:54 ` Andrew Burgess
2025-10-06 15:39 ` Tom Tromey
2025-10-06 16:13 ` Andrew Burgess
2025-09-23 13:44 ` [PATCHv2 2/3] gdb: make structured core file mappings processing global Andrew Burgess
2025-10-13 13:57 ` Lancelot SIX
2025-10-13 14:37 ` Andrew Burgess
2025-10-13 15:16 ` Six, Lancelot
2025-10-14 9:12 ` Lancelot SIX
2025-09-23 13:44 ` [PATCHv2 3/3] gdb/python: add Corefile.mapped_files method Andrew Burgess
2025-10-03 19:15 ` Tom Tromey
2025-10-07 6:24 ` Tom de Vries
2025-10-07 12:21 ` Andrew Burgess
2025-10-07 13:08 ` Tom de Vries
2025-10-07 13:26 ` Andrew Burgess
2025-10-07 14:38 ` Andrew Burgess
2025-10-07 15:43 ` Tom de Vries
2025-10-07 16:28 ` Andrew Burgess
2025-10-08 9:29 ` Andrew Burgess
2025-10-08 10:36 ` Tom de Vries
2025-10-08 14:14 ` Andrew Burgess
2025-10-08 15:43 ` Tom de Vries
2025-10-08 16:03 ` Andrew Burgess
2025-10-16 20:00 ` Tom Tromey
2025-10-17 10:02 ` Andrew Burgess
2025-10-17 13:32 ` 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.1758634958.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