From: Matthieu Longo <matthieu.longo@arm.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v1 1/4] gdb/python: add gdbpy_borrowed_ref
Date: Thu, 23 Apr 2026 18:31:36 +0100 [thread overview]
Message-ID: <ff8adbb8-d69c-44af-afd0-b3995e7cd9a7@arm.com> (raw)
In-Reply-To: <87340ttx27.fsf@tromey.com>
On 17/04/2026 16:40, Tom Tromey wrote:
>>>>>> Matthieu Longo <matthieu.longo@arm.com> writes:
>
>> From: Tom Tromey <tom@tromey.com>
>> This adds a new gdbpy_borrowed_ref class. This class is primarily for
>> code "documentation" purposes -- it makes it clear to the reader that
>> a given reference is borrowed. However, it also adds a tiny bit of
>> safety, in that conversion to gdbpy_ref<> will acquire a new
>> reference.
>
> On my branch I ended up giving this a gdbpy_opt_borrowed_ref base class.
>
Is this branch public ?
>> +/* A class representing a borrowed reference.
>> +
>> + 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 guaranteed to make a new
>> + reference. */
>> +template <class T = PyObject>
>> +class gdbpy_borrowed_ref
>
> Also mine isn't templated like this though I guess this makes some
> sense.
>
This templating is handy when you need to access fields from the subclass.
> IIRC I felt like this was overkill. I didn't read your subsequent
> patches yet but I assume there's some use for it.
>
For instance, :
static PyObject *
pyuw_create_unwind_info (gdbpy_borrowed_ref<pending_frame_object> pyo_pending_frame,
struct frame_id frame_id)
{
gdb_assert (pyo_pending_frame->frame_info != nullptr);
gdbpy_heap_type_allocate_or_bailout (unwind_info_wrapper,
unwind_info_object,
unwind_info_object_type);
unwind_info_wrapper->frame_id = frame_id;
unwind_info_wrapper->pending_frame
= pyo_pending_frame.strong_ref ().release ();
unwind_info_wrapper->saved_regs = new std::vector<saved_reg>;
return unwind_info_wrapper.track ().release ();
}
>> + /* Allow a (checked) conversion to any subclass of PyObject. */
>> + template<typename TObj,
>> + typename = std::is_convertible<TObj *, T *>>
>> + operator TObj * ()
>> + {
>> + //gdb_assert (PyObject_TypeCheck (m_obj, T::corresponding_object_type));
>
> No commented-out code. This is unsafe though. I would prefer a check.
>
> I think a name other than "TObj" would be good.
> Even "U" would be better. "T" and "TObj" are too close.
>
I deleted this method, it was not needed.
>> + /* When converting a borrowed reference to a gdbpy_ref<>, a new
>> + reference is acquired. */
>> + template <typename TObj,
>> + typename = std::is_convertible<TObj *, T *>>
>> + operator gdbpy_ref<TObj> ()
>> + {
>> + gdb_assert (m_obj != nullptr);
>> + return gdbpy_ref<TObj>::new_reference (m_obj);
>> + }
>
> The naming thing here too. And also safety if we can get it.
>
Replaced TObj by U.
/* When converting a borrowed reference to a gdbpy_ref<>, a new
reference is acquired. */
template <typename U,
typename = std::is_convertible<U *, T *>>
operator gdbpy_ref<U> ()
{
if (m_obj != nullptr)
return gdbpy_ref<U>::new_reference (m_obj);
return nullptr;
}
>> +
>> + gdbpy_ref<T> strong_ref () const noexcept
>> + {
>> + return static_cast<gdbpy_ref<T>> (*this);
>> + }
>
> I think it would be clearer to directly write this in terms of
> new_reference.
/* Convert a borrowed reference to a strong one, i.e. gdbpy_ref<>. */
gdbpy_ref<T> strong_ref () const noexcept
{
if (m_obj != nullptr)
return gdbpy_ref<T>::new_reference (m_obj);
return nullptr;
}
>
> Tom
Here is the complete version with the modification.
Matthieu
/* A class representing a borrowed reference.
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 guaranteed to make a new
reference. */
template <class T = PyObject>
class gdbpy_borrowed_ref
{
public:
gdbpy_borrowed_ref () noexcept
: m_obj (nullptr)
{
}
gdbpy_borrowed_ref (const std::nullptr_t) noexcept
: m_obj (nullptr)
{
}
template <typename U,
typename = std::is_convertible<U *, T*>>
gdbpy_borrowed_ref (U *obj) noexcept
: m_obj (obj)
{
}
template <typename U,
typename = std::is_convertible<U *, T*>>
gdbpy_borrowed_ref (const gdbpy_ref<U> &ref) noexcept
: m_obj (ref.get ())
{
}
gdbpy_borrowed_ref (const gdbpy_borrowed_ref &other) noexcept
: m_obj (other.m_obj)
{
}
gdbpy_borrowed_ref &operator= (const gdbpy_borrowed_ref &other)
{
m_obj = other.m_obj;
return *this;
}
operator T * () const noexcept
{
return m_obj;
}
/* Explicit version of the previous implicit cast operator. */
T *get () const noexcept
{
return m_obj;
}
/* When converting a borrowed reference to a gdbpy_ref<>, a new
reference is acquired. */
template <typename U,
typename = std::is_convertible<U *, T *>>
operator gdbpy_ref<U> ()
{
if (m_obj != nullptr)
return gdbpy_ref<U>::new_reference (m_obj);
return nullptr;
}
/* Convert a borrowed reference to a strong one, i.e. gdbpy_ref<>. */
gdbpy_ref<T> strong_ref () const noexcept
{
if (m_obj != nullptr)
return gdbpy_ref<T>::new_reference (m_obj);
return nullptr;
}
/* Let users refer to members of the underlying pointer. */
T *operator-> () const noexcept
{
return m_obj;
}
private:
T *m_obj;
};
next prev parent reply other threads:[~2026-04-23 17:33 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 10:51 [PATCH v1 0/4] gdb/python: more fixes again for Python limited C API support Matthieu Longo
2026-04-09 10:51 ` [PATCH v1 1/4] gdb/python: add gdbpy_borrowed_ref Matthieu Longo
2026-04-17 15:40 ` Tom Tromey
2026-04-23 17:31 ` Matthieu Longo [this message]
2026-04-09 10:51 ` [PATCH v1 2/4] gdb/python: eval_python_command returns both exit code and result Matthieu Longo
2026-04-17 17:22 ` Tom Tromey
2026-04-23 19:11 ` Matthieu Longo
2026-04-09 10:51 ` [PATCH v1 3/4] gdb/python: migrate Python initialization to use the new config API (PEP 741) Matthieu Longo
2026-04-17 15:53 ` Tom Tromey
2026-04-24 9:41 ` Matthieu Longo
2026-04-24 14:56 ` Tom Tromey
2026-04-27 15:12 ` Matthieu Longo
2026-04-28 14:44 ` Tom Tromey
2026-04-09 10:51 ` [PATCH v1 4/4] gdb/python: work around missing symbols not yet part of Python limited API Matthieu Longo
2026-04-17 17:26 ` Tom Tromey
2026-04-24 10:14 ` Matthieu Longo
2026-04-15 9:18 ` [PATCH v1 0/4] gdb/python: more fixes again for Python limited C API support Matthieu Longo
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=ff8adbb8-d69c-44af-afd0-b3995e7cd9a7@arm.com \
--to=matthieu.longo@arm.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.com \
/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