From: Matthieu Longo <matthieu.longo@arm.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org, Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH v1] gdb/python: fix memory leak in gdb_py_tp_name
Date: Fri, 29 May 2026 11:08:02 +0100 [thread overview]
Message-ID: <f3f32ff4-f378-4037-b37f-39a0cad238e9@arm.com> (raw)
In-Reply-To: <87ldd35php.fsf@tromey.com>
On 28/05/2026 20:00, Tom Tromey wrote:
>>>>>> "Matthieu" == Matthieu Longo <matthieu.longo@arm.com> writes:
>
> Matthieu> Indeed that can happen, for instance, when this function is called
> Matthieu> inside a tp_clear() in the middle of a PyObject destruction.
>
> Thanks.
>
> Matthieu> Something like below would at least avoid the general abort, but it
> Matthieu> would cause logging of errors in the middle of the destruction. How
> Matthieu> useful would it be ?
>
> Matthieu> gdbpy_ref<> fully_qualified_name (PyType_GetFullyQualifiedName (py_type));
> Matthieu> if (fully_qualified_name == nullptr)
> Matthieu> {
> Matthieu> PyErr_Print();
> Matthieu> PyErr_Clear();
> Matthieu> return {};
> Matthieu> }
>
> Matthieu> At this point, I don't think that it is super important not to crash
> Matthieu> because there is a serious logic error somewhere if we are unable to
> Matthieu> get this name. Consequently, an assert might be more appropriate.
>
> If we think it could conceivably happen then it should probably just
> call gdbpy_print_stack (which is basically the above but with some user
> controls) and then return some error string.
>
> Tom
What about the below ?
Matthieu
diff --git a/gdb/python/py-obj-type.c b/gdb/python/py-obj-type.c
index 45f7d8a3d74..514dbf5c179 100644
--- a/gdb/python/py-obj-type.c
+++ b/gdb/python/py-obj-type.c
@@ -27,7 +27,11 @@ gdb_py_tp_name (PyTypeObject *py_type) noexcept
auto pyobj_to_str = [](PyObject *name) -> std::string
{
const char *s = PyUnicode_AsUTF8AndSize (name, nullptr);
- return (s == nullptr) ? "" : s;
+ if (s != nullptr)
+ return s;
+
+ gdbpy_print_stack ();
+ error (_("Could not convert PyObject to UTF-8 string."));
};
#if PY_VERSION_HEX >= 0x030d0000
@@ -35,8 +39,10 @@ gdb_py_tp_name (PyTypeObject *py_type) noexcept
part of the stable ABI since version 3.13. */
gdbpy_ref<> fully_qualified_name (PyType_GetFullyQualifiedName (py_type));
if (fully_qualified_name == nullptr)
- return {};
-
+ {
+ gdbpy_print_stack ();
+ error (_("Could not get fully qualified name."));
+ }
return pyobj_to_str (fully_qualified_name.get ());
#else /* PY_VERSION_HEX < 0x030d0000 && ! defined (Py_LIMITED_API) */
@@ -52,8 +58,10 @@ gdb_py_tp_name (PyTypeObject *py_type) noexcept
/* Note: PyType_GetQualName() was added in version 3.11. */
gdbpy_ref<> qualname (PyType_GetQualName (py_type));
if (qualname == nullptr)
- return {};
-
+ {
+ gdbpy_print_stack ();
+ error (_("Could not get qualified name."));
+ }
return pyobj_to_str (qualname.get ());
# else
@@ -64,8 +72,10 @@ gdb_py_tp_name (PyTypeObject *py_type) noexcept
when the minimum supported Python version is increased above 3.10. */
PyHeapTypeObject *ht = (PyHeapTypeObject *) py_type;
if (ht->ht_qualname == nullptr)
- return {};
-
+ {
+ gdbpy_print_stack ();
+ error (_("Could not get qualified name."));
+ }
return pyobj_to_str (ht->ht_qualname);
# endif
#endif
next prev parent reply other threads:[~2026-05-29 10:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 16:04 Matthieu Longo
2026-05-26 16:35 ` Tom Tromey
2026-05-28 12:46 ` Matthieu Longo
2026-05-28 16:43 ` Tom Tromey
2026-05-28 17:08 ` Matthieu Longo
2026-05-28 19:00 ` Tom Tromey
2026-05-29 10:08 ` Matthieu Longo [this message]
2026-05-29 10:52 ` Andrew Burgess
2026-05-29 13:09 ` Tom Tromey
2026-06-01 9:57 ` Matthieu Longo
2026-06-02 9:36 ` Andrew Burgess
2026-06-02 14:22 ` Tom Tromey
2026-06-03 16:30 ` Matthieu Longo
2026-06-04 9:30 ` Andrew Burgess
2026-06-05 20:49 ` Tom Tromey
2026-06-08 10:31 ` Matthieu Longo
2026-06-08 18:51 ` Andrew Burgess
2026-06-05 10:06 ` Tom de Vries
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=f3f32ff4-f378-4037-b37f-39a0cad238e9@arm.com \
--to=matthieu.longo@arm.com \
--cc=aburgess@redhat.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