From: Tom Tromey <tom@tromey.com>
To: Matthieu Longo <matthieu.longo@arm.com>
Cc: <gdb-patches@sourceware.org>, Tom Tromey <tom@tromey.com>
Subject: Re: [PATCH v2 4/4] gdb/python: work around missing symbols not yet part of Python limited API
Date: Thu, 14 May 2026 13:26:45 -0600 [thread overview]
Message-ID: <871pfdkd1m.fsf@tromey.com> (raw)
In-Reply-To: <20260428162416.511367-5-matthieu.longo@arm.com> (Matthieu Longo's message of "Tue, 28 Apr 2026 17:24:16 +0100")
>>>>> Matthieu Longo <matthieu.longo@arm.com> writes:
> This patch adds a new header, python-limited-api-missing.h, which
> exposes symbols not yet part of the Python limited API.
This is ok.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
next prev parent reply other threads:[~2026-05-14 19:27 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-28 16:24 [PATCH v2 0/4] gdb/python: more fixes again for Python limited C API support Matthieu Longo
2026-04-28 16:24 ` [PATCH v2 1/4] gdb/python: add gdbpy_borrowed_ref Matthieu Longo
2026-05-15 16:56 ` Tom Tromey
2026-05-18 14:25 ` Matthieu Longo
2026-05-19 19:25 ` Tom Tromey
2026-05-20 16:04 ` Matthieu Longo
2026-05-21 14:35 ` Tom Tromey
2026-05-21 23:18 ` Tom Tromey
2026-04-28 16:24 ` [PATCH v2 2/4] gdb/python: eval_python_command returns result of the evaluation Matthieu Longo
2026-05-15 16:51 ` Tom Tromey
2026-05-18 14:37 ` Matthieu Longo
2026-05-19 19:24 ` Tom Tromey
2026-05-20 10:07 ` Matthieu Longo
2026-05-20 15:06 ` Tom Tromey
2026-04-28 16:24 ` [PATCH v2 3/4] gdb/python: migrate Python initialization to use the new config API (PEP 741) Matthieu Longo
2026-05-14 19:25 ` Tom Tromey
2026-04-28 16:24 ` [PATCH v2 4/4] gdb/python: work around missing symbols not yet part of Python limited API Matthieu Longo
2026-05-14 19:26 ` Tom Tromey [this message]
2026-05-15 10:10 ` Matthieu Longo
2026-05-14 10:23 ` [PATCH v2 0/4] gdb/python: more fixes again for Python limited C API support Matthieu Longo
2026-05-14 19:27 ` Tom Tromey
2026-05-15 9:26 ` Matthieu Longo
2026-05-15 14:48 ` 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=871pfdkd1m.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=matthieu.longo@arm.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