From: Andrew Burgess via Gdb <gdb@sourceware.org>
To: Matthieu Longo <matthieu.longo@arm.com>, Tom Tromey <tom@tromey.com>
Cc: gdb@sourceware.org
Subject: Re: RFC: prototype of C extensions using the Python limited API
Date: Wed, 10 Jun 2026 17:10:20 +0100 [thread overview]
Message-ID: <87v7bqpeab.fsf@redhat.com> (raw)
In-Reply-To: <a13ee16e-80ac-41e1-bf9f-be35fe482a01@arm.com>
Matthieu Longo <matthieu.longo@arm.com> writes:
> On 01/06/2026 11:10, Matthieu Longo via Gdb wrote:
>> On 28/05/2026 17:31, Matthieu Longo via Gdb wrote:
>>> On 28/05/2026 17:24, Matthieu Longo via Gdb wrote:
>>>> Hi Tom,
>>>>
>>>> As I previously told you (at least, I believe so but I am not 100% sure), I finished migrating all
>>>> the Python C extensions some time ago. I had discovered some issues with a case of inheritance
>>>> causing unexpected crashes.
>>>> To facilitate the debugging, I decided to implement a prototype outside of GDB, and managed to make
>>>> it work. I finally got the prototype reviewed by Victor Stinner, a Python core developer, to double-
>>>> check whether my design was working as expected.
>>>>
>>>> Please find attached my last iteration. I also provided an archive which should be more convenient
>>>> for you if you want to compile and test it.
>>>>
>>>> Could you please review it so that we validate this new approach before I migrate all my previous
>>>> patches to it ?
>>>>
>>>> PS:
>>>> - a README is provided with all the needed instruction inside.
>>>> - this patch contains code from outside GDB's repository, and should not be merged inside GDB's
>>>> repository.
>>>>
>>>> Regards,
>>>> Matthieu
>>>
>>> With the archive, hopefully not inlined.
>>
>> Hi Tom,
>>
>> Any chance for you to have a look at this in the next two weeks ?
>>
>> Matthieu
>
> Ping.
> Adding Andrew too in the loop.
Would it be possible to give a brief explanation for what this is all
about? When reviewing something I usually start by reading the
description and then check the code matches what was written, but your
text doesn't really help me ... I suspect there's some back story that
I'm missing, but it would be neat if that could all be summarised, or at
least links to it added, here.
Thanks,
Andrew
next prev parent reply other threads:[~2026-06-10 16:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 16:24 Matthieu Longo via Gdb
2026-05-28 16:31 ` Matthieu Longo via Gdb
2026-06-01 10:10 ` Matthieu Longo via Gdb
2026-06-08 13:38 ` Matthieu Longo via Gdb
2026-06-10 16:10 ` Andrew Burgess via Gdb [this message]
2026-06-16 17:15 ` Matthieu Longo via Gdb
2026-06-18 20:46 ` Tom Tromey
2026-06-22 9:26 ` Matthieu Longo via Gdb
2026-06-29 10:37 ` Matthieu Longo via Gdb
2026-06-22 10:24 ` Matthieu Longo via Gdb
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=87v7bqpeab.fsf@redhat.com \
--to=gdb@sourceware.org \
--cc=aburgess@redhat.com \
--cc=matthieu.longo@arm.com \
--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