From: Matthieu Longo via Gdb <gdb@sourceware.org>
To: Tom Tromey <tom@tromey.com>, gdb@sourceware.org
Cc: Andrew Burgess <aburgess@redhat.com>
Subject: Re: Prototype of C extension using Python limited API
Date: Thu, 28 May 2026 17:30:07 +0100 [thread overview]
Message-ID: <1767a089-ddbd-4991-9434-1b9ea7492e9b@arm.com> (raw)
In-Reply-To: <cd69fcb3-d689-440d-b05e-61e8e4ca4f1c@arm.com>
On 28/05/2026 17:25, 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
Please ignore this email.
This is a duplicate of https://inbox.sourceware.org/gdb/21479c1d-3a9a-4ae2-bc1a-5dc19871f275@arm.com/
prev parent reply other threads:[~2026-05-28 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-28 16:25 Matthieu Longo via Gdb
2026-05-28 16:30 ` 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=1767a089-ddbd-4991-9434-1b9ea7492e9b@arm.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