From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/4] Convert py-frame.c to Python safety API
Date: Wed, 19 Aug 2026 17:54:38 -0600 [thread overview]
Message-ID: <20260819-python-safety-frame-v1-0-563cb6b9e7a6@tromey.com> (raw)
This series converts py-frame.c to the Python safety API.
I've split it into multiple parts to make it perhaps a bit easier to
review. Often I find these patches pretty hard to read, since they
involve converting a bunch of functions into methods, making them
fairly messy.
A few FIXME comments are added; as with other cases, these can all be
removed once the conversion is complete. At the current rate this may
be a while.
Tested on x86-64 Fedora 40.
Signed-off-by: Tom Tromey <tom@tromey.com>
---
Tom Tromey (4):
Basic safety conversion of py-frame.c
Convert gdbpy_newest_frame and gdbpy_selected_frame to safety API
Convert gdbpy_frame_stop_reason_string to the safety API
Convert frapy_richcompare to safety API
gdb/python/py-frame.c | 852 +++++++++++++---------------------
gdb/python/py-inferior.c | 24 +-
gdb/python/py-safety.h | 53 +++
gdb/python/python-internal.h | 7 +-
gdb/python/python.c | 12 +-
gdb/testsuite/gdb.python/py-frame.exp | 3 +
6 files changed, 408 insertions(+), 543 deletions(-)
---
base-commit: 07ee9e316ab6d53b5ed1aae8fe7448a559abe4be
change-id: 20260819-python-safety-frame-c795afcc47df
Best regards,
--
Tom Tromey <tom@tromey.com>
next reply other threads:[~2026-08-19 23:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-19 23:54 Tom Tromey [this message]
2026-08-19 23:54 ` [PATCH 1/4] Basic safety conversion of py-frame.c Tom Tromey
2026-08-19 23:54 ` [PATCH 2/4] Convert gdbpy_newest_frame and gdbpy_selected_frame to safety API Tom Tromey
2026-08-19 23:54 ` [PATCH 3/4] Convert gdbpy_frame_stop_reason_string to the " Tom Tromey
2026-08-19 23:54 ` [PATCH 4/4] Convert frapy_richcompare to " 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=20260819-python-safety-frame-v1-0-563cb6b9e7a6@tromey.com \
--to=tom@tromey.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