From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 1/4] Add gdbpy_borrowed_ref
Date: Fri, 15 May 2026 12:23:19 -0600 [thread overview]
Message-ID: <20260515-python-safety-initial-v1-1-8f155338df57@tromey.com> (raw)
In-Reply-To: <20260515-python-safety-initial-v1-0-8f155338df57@tromey.com>
This adds new gdbpy_opt_borrowed_ref and gdbpy_borrowed_ref classes.
These class is primarily for code "documentation" purposes -- it makes
it clear to the reader that a given reference is borrowed. However,
they also add a tiny bit of safety, in that conversion to gdbpy_ref<>
will either be rejected (by the "opt" class) or acquire a new
reference.
---
gdb/python/py-ref.h | 80 +++++++++++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 80 insertions(+)
diff --git a/gdb/python/py-ref.h b/gdb/python/py-ref.h
index dc0b14814af..ef6b9fb427c 100644
--- a/gdb/python/py-ref.h
+++ b/gdb/python/py-ref.h
@@ -41,6 +41,86 @@ struct gdbpy_ref_policy
template<typename T = PyObject> using gdbpy_ref
= gdb::ref_ptr<T, gdbpy_ref_policy>;
+/* A class representing an optional borrowed reference. It is
+ "optional" because NULL is a valid value.
+
+ This is a simple wrapper for a PyObject*. Aside from documenting
+ what the code does, the main advantage of using this is that
+ conversion to a gdbpy_ref<> is prevented.
+
+ An optional borrowed reference is only used in situations where
+ Python says NULL is valid. For example, it is used as the type of
+ the "keywords" argument to a varargs method. Most code should
+ prefer an ordinary gdbpy_borrowed_ref, see below. */
+class gdbpy_opt_borrowed_ref
+{
+public:
+
+ gdbpy_opt_borrowed_ref (PyObject *obj)
+ : m_obj (obj)
+ {
+ }
+
+ template<typename T>
+ gdbpy_opt_borrowed_ref (const gdbpy_ref<T> &ref)
+ : m_obj (ref.get ())
+ {
+ }
+
+ operator PyObject * ()
+ {
+ return m_obj;
+ }
+
+ operator gdbpy_ref<> () = delete;
+
+protected:
+ PyObject *m_obj;
+};
+
+/* A borrowed reference that is guaranteed not to be NULL.
+
+ Like gdbpy_opt_borrowed_ref, this mostly serves a documentary
+ purpose. However, it also allows a checked cast to any subclass of
+ PyObject, and conversion to a gdbpy_ref<> will automatically
+ acquire a new reference -- a safety improvement over plain
+ PyObject*. */
+class gdbpy_borrowed_ref : public gdbpy_opt_borrowed_ref
+{
+public:
+
+ gdbpy_borrowed_ref (PyObject *obj)
+ : gdbpy_opt_borrowed_ref (obj)
+ {
+ gdb_assert (m_obj != nullptr);
+ }
+
+ template<typename T>
+ gdbpy_borrowed_ref (const gdbpy_ref<T> &ref)
+ : gdbpy_opt_borrowed_ref (ref)
+ {
+ gdb_assert (m_obj != nullptr);
+ }
+
+ gdbpy_borrowed_ref (std::nullptr_t) = delete;
+
+ /* Allow a (checked) conversion to any subclass of PyObject. */
+ template<typename T,
+ typename = std::is_convertible<T *, PyObject *>>
+ operator T * ()
+ {
+ gdb_assert (PyObject_TypeCheck (m_obj, T::corresponding_object_type));
+ return static_cast<T *> (m_obj);
+ }
+
+ /* When converting a borrowed reference to a gdbpy_ref<>, a new
+ reference is acquired. */
+ operator gdbpy_ref<> ()
+ {
+ return gdbpy_ref<>::new_reference (m_obj);
+ }
+};
+
/* A wrapper class for Python extension objects that have a __dict__ attribute.
Any Python C object extension needing __dict__ should inherit from this
--
2.49.0
next prev parent reply other threads:[~2026-05-15 18:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-15 18:23 [PATCH 0/4] Python safety initial work Tom Tromey
2026-05-15 18:23 ` Tom Tromey [this message]
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-1-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