From: Matthieu Longo <matthieu.longo@arm.com>
To: Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 9/9] gdb/python: add accessor helpers for __dict__ in Python extension objects
Date: Fri, 6 Mar 2026 14:33:31 +0000 [thread overview]
Message-ID: <f94813c5-8c3e-44fa-a7da-009916420a8d@arm.com> (raw)
In-Reply-To: <87zf4opwhz.fsf@tromey.com>
On 03/03/2026 19:02, Tom Tromey wrote:
>>>>>> Matthieu Longo <matthieu.longo@arm.com> writes:
>
>> A previous patch centralized the creation logic; this patch focuses
>> on centralizing the access to the dictionary. It introduces two new
>> macros:
>
> Thanks.
>
>
>> + #define gdbpy_dict_wrapper_PyGetSetDef(object_name) \
>> + { \
>> + "__dict__", /* name */ \
>> + (getter) gdb_py_generic_dict_getter, \
>> + (setter) nullptr, \
>> + "The __dict__ for this " object_name ".", /* doc */ \
>> + nullptr, /* closure */ \
>> + }
>> +
>> + #define gdbpy_dict_wrapper_PyTypeObject_tps \
>> + /*tp_getattro*/ \
>> + gdb_py_generic_getattro, \
>> + /*tp_setattro*/ \
>> + gdb_py_generic_setattro
>
> I wouldn't indent the '#define'. But I tend to think it would be better
> to just use constexpr functions here.
>
For gdbpy_dict_wrapper_PyGetSetDef, I tried to use a constexpr function at first, but there is an issue.
I am not aware of an easy way to concatenate strings with a constexpr in C++17.
This code requires C++20.
static constexpr PyGetSetDef
configure_dict_getter (std::string_view object_name)
{
return {
"__dict__", /* name */
(getter) gdb_py_generic_dict_getter,
(setter) nullptr,
std::views::join (std::array {
"The __dict__ for this "sv, object_name, "."sv
}).data (), /* doc */
nullptr, /* closure */
}
}
Please let me know if you know a way of making it compatible with C++17.
Regarding gdbpy_dict_wrapper_PyTypeObject_tps, I am not sure how to expand the array in the calling code using a constexpr function.
Please let me know if you know a solution for it.
> I'd also suggest changing the name, the "PyGetSetDef" suffix is kind of
> un-gdb-ish and anyway not really needed for a function, since this will
> be clear from the return type.
>
If the code is convertible to C++17, configure_dict_getter seems a good name.
Otherwise, gdbpy_dict_wrapper_configure_dict_getter ?
Regarding gdbpy_dict_wrapper_PyTypeObject_tps, what about gdbpy_dict_wrapper_getsetattro ?
> You can see an example of doing this in a similar-ish context here
>
> https://sourceware.org/pipermail/gdb-patches/2026-February/225253.html
>
> Tom
Matthieu
next prev parent reply other threads:[~2026-03-06 14:35 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-03 16:16 [PATCH v2 0/9] gdb: more fixes for Python limited C API support Matthieu Longo
2026-03-03 16:16 ` [PATCH v2 1/9] gdb: switch tuple object helpers to Python limited API equivalents Matthieu Longo
2026-03-03 18:09 ` Tom Tromey
2026-03-03 16:16 ` [PATCH v2 2/9] gdb: introduce rgb_color type to simplify existing code Matthieu Longo
2026-03-03 18:16 ` Tom Tromey
2026-03-04 16:30 ` Matthieu Longo
2026-03-03 16:16 ` [PATCH v2 3/9] gdb: switch bytes object helpers to Python limited API equivalents Matthieu Longo
2026-03-03 18:03 ` Tom Tromey
2026-03-03 16:16 ` [PATCH v2 4/9] gdb: add new helpers for retrieving a type's fully qualified name Matthieu Longo
2026-03-03 18:59 ` Tom Tromey
2026-03-06 17:49 ` Matthieu Longo
2026-03-06 19:45 ` Tom Tromey
2026-03-03 16:16 ` [PATCH v2 5/9] gdb/python: allow ref_ptr<T, Policy>::new_reference to accept subclasses of T Matthieu Longo
2026-03-03 18:18 ` Tom Tromey
2026-03-04 16:56 ` Matthieu Longo
2026-03-04 18:55 ` Tom Tromey
2026-03-06 11:37 ` Matthieu Longo
2026-03-06 11:43 ` Matthieu Longo
2026-03-06 16:47 ` Tom Tromey
2026-03-09 11:38 ` Matthieu Longo
2026-03-03 16:16 ` [PATCH v2 6/9] gdb/python: flatten functions calling PyObject_New and use gdbpy_ref Matthieu Longo
2026-03-03 18:22 ` Tom Tromey
2026-03-09 11:41 ` Matthieu Longo
2026-03-03 18:22 ` Tom Tromey
2026-03-03 16:16 ` [PATCH v2 7/9] gdb/python: accept gdbpy_ref in init helpers and return bool Matthieu Longo
2026-03-03 18:24 ` Tom Tromey
2026-03-09 13:25 ` Matthieu Longo
2026-03-03 16:16 ` [PATCH v2 8/9] gdb/python: add gdbpy_dict_wrapper:allocate_dict helper Matthieu Longo
2026-03-03 18:30 ` Tom Tromey
2026-03-06 12:03 ` Matthieu Longo
2026-03-03 16:16 ` [PATCH v2 9/9] gdb/python: add accessor helpers for __dict__ in Python extension objects Matthieu Longo
2026-03-03 19:02 ` Tom Tromey
2026-03-06 14:33 ` Matthieu Longo [this message]
2026-03-06 16:04 ` 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=f94813c5-8c3e-44fa-a7da-009916420a8d@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