Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Matthieu Longo via Gdb <gdb@sourceware.org>
To: Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>, Tom de Vries <tdevries@suse.de>
Subject: Re: RFC: prototype of C extensions using the Python limited API
Date: Thu, 20 Aug 2026 14:59:07 +0100	[thread overview]
Message-ID: <f4b4074b-c547-4948-ae47-86ccb0e722d6@arm.com> (raw)
In-Reply-To: <143b06a7-117f-4500-a911-26f8f79eef2f@arm.com>

On 22/06/2026 11:24, 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
> 
> This might be easier to review.
> 
> Matthieu
Hi Tom,

I noticed that lately, Tom de Vries and you have been working on porting the existing Python C
extensions to use the Python safety API you proposed some time ago. That's good to see some progress
on this side as I might use some of the introduced structures into my patches.

However, those patches have created a significant amount of conflicts on my development branch.
And since I haven't heard of you for a while regarding this prototype, should I understand that you
would prefer to prioritize the migration to the safe API before the migration to the limited API ?

Also, do you think that it would be helpful to discuss over a zoom call the status of the limited
API migration, the prototype, and what is remaining to be done ?

Please, let me know about your thoughts.

Note: adding Tom de Vries in CC as he is working on the Python C extensions, and might be interested
in the discussion.

Regards,
Matthieu

      reply	other threads:[~2026-08-20 14:00 UTC|newest]

Thread overview: 11+ 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
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
2026-08-20 13:59   ` Matthieu Longo via Gdb [this message]

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=f4b4074b-c547-4948-ae47-86ccb0e722d6@arm.com \
    --to=gdb@sourceware.org \
    --cc=aburgess@redhat.com \
    --cc=matthieu.longo@arm.com \
    --cc=tdevries@suse.de \
    --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