From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/4] Python safety initial work
Date: Fri, 15 May 2026 12:23:18 -0600 [thread overview]
Message-ID: <20260515-python-safety-initial-v1-0-8f155338df57@tromey.com> (raw)
I rewrote my earlier Python safety series to use methods a while back.
And while I like the result, I got bogged down converting things, so I
thought I'd send some initial work, with the idea that if this looks
good, other code can be transformed in pieces.
Since this is extracted from a larger series, there is some code in
here that isn't currently used in-tree. This is mainly true for the
gdb functions that wrap Python APIs, see patch 2.
Patch 4 shows what the end effect is, but the patch is somewhat hard
to read IMO. So for instance now the 'title' getter for a TUI window
is just an ordinary method:
const std::string &
gdbpy_tui_window::title ()
{
require_valid ();
return window->title ();
}
Since it wants to only operate on a valid window, require_valid will
throw if that isn't the case.
Note there's no explicit error checking, no casts, no messing with
reference counts, and the return type is just a string. All these
boilerplate details are handled by a template wrapper function.
Signed-off-by: Tom Tromey <tom@tromey.com>
---
Tom Tromey (4):
Add gdbpy_borrowed_ref
Add wrappers for some Python APIs
Add wrappers for Python implementation functions and methods
Convert py-tui.c to the "python safety" approach
gdb/python/py-ref.h | 80 +++++++++++
gdb/python/py-safety.h | 321 +++++++++++++++++++++++++++++++++++++++++
gdb/python/py-tui.c | 208 +++++++++++----------------
gdb/python/py-wrappers.h | 334 +++++++++++++++++++++++++++++++++++++++++++
gdb/python/python-internal.h | 8 +-
gdb/python/python.c | 5 +-
6 files changed, 830 insertions(+), 126 deletions(-)
---
base-commit: 776715ea683b93c0415fc4eb31b4fcec5f2153fc
change-id: 20260515-python-safety-initial-422bf34a8ce3
Best regards,
--
Tom Tromey <tom@tromey.com>
next reply other threads:[~2026-05-15 18:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 18:23 Tom Tromey [this message]
2026-05-15 18:23 ` [PATCH 1/4] Add gdbpy_borrowed_ref Tom Tromey
2026-05-15 18:23 ` [PATCH 2/4] Add wrappers for some Python APIs Tom Tromey
2026-05-15 18:23 ` [PATCH 3/4] Add wrappers for Python implementation functions and methods Tom Tromey
2026-05-15 18:23 ` [PATCH 4/4] Convert py-tui.c to the "python safety" approach 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=20260515-python-safety-initial-v1-0-8f155338df57@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