From: Simon Marchi <simark@simark.ca>
To: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Use Python safety API in py-symbol.c
Date: Thu, 13 Aug 2026 10:43:11 -0400 [thread overview]
Message-ID: <997f9830-eeb3-4339-895d-38ba74d3fe45@simark.ca> (raw)
In-Reply-To: <20260811002538.1177538-1-tom@tromey.com>
On 8/10/26 8:25 PM, Tom Tromey wrote:
> This changes py-symbol.c to use the new Python safety API.
>
> v2 changes gdb.Symbol.value to accept keyword arguments. A new test
> is added.
>
> Regression tested on x86-64 Fedora 40.
I haven't followed the Python safety work much, but the patch LGTM.
The include of "top.h" can now be removed.
Do we need a NEWS entry for the `frame` keyword argument, or it's too
minor?
Approved-By: Simon Marchi <simon.marchi@efficios.com>
Simon
next prev parent reply other threads:[~2026-08-13 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-11 0:25 Tom Tromey
2026-08-13 14:43 ` Simon Marchi [this message]
2026-08-13 20:42 ` 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=997f9830-eeb3-4339-895d-38ba74d3fe45@simark.ca \
--to=simark@simark.ca \
--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