From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: Tom Tromey <tom@tromey.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH v3 0/4] Python safety initial work
Date: Fri, 07 Aug 2026 13:48:27 -0600 [thread overview]
Message-ID: <87ldahyano.fsf@tromey.com> (raw)
In-Reply-To: <464776ce-eadc-4ad9-8757-87e4457c7ce9@suse.de> (Tom de Vries's message of "Tue, 21 Jul 2026 13:45:58 +0200")
>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:
Tom> I found this code:
Tom> ...
Tom> /* Note this returns a borrowed reference. */
Tom> PyObject *arg = PyTuple_GetItem (args, i);
Tom> ...
Tom> and decided to try to convert all PyTuple_GetItem calls. The result
Tom> of that exercise is attached.
Tom> I ended up also touching the wrapper function:
Tom> ...
Tom> static inline gdbpy_borrowed_ref<>
Tom> gdbpy_tuple_get_item (gdbpy_borrowed_ref<> tuple, Py_ssize_t pos)
Tom> {
Tom> - PyObject *result = PyTuple_GetItem (tuple, pos);
Tom> + gdbpy_opt_borrowed_ref<> result = PyTuple_GetItem (tuple, pos);
Tom> if (result == nullptr)
Tom> throw gdb_python_exception ();
Tom> - return result;
Tom> + return (PyObject *)result;
Tom> }
Tom> ...
Tom> but perhaps you left that out intentionally?
Yeah, in this spot it didn't seem to really be necessary.
The idea of the wrapper file is to eventually isolate all "raw" calls to
the Python API.
Tom> I haven't used the gdbpy_tuple_get_item wrapper, AFAICT it was not
Tom> applicable.
The long term goal is to convert everything to call the wrappers.
This way exception handling will be enforced.
Tom
next prev parent reply other threads:[~2026-08-07 19:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-21 23:27 Tom Tromey
2026-05-21 23:27 ` [PATCH v3 1/4] Add gdbpy_borrowed_ref Tom Tromey
2026-06-01 10:00 ` Matthieu Longo
2026-06-03 18:19 ` Tom Tromey
2026-07-24 12:02 ` Yury Khrustalev
2026-08-14 15:43 ` Matthieu Longo
2026-06-29 13:51 ` Matthieu Longo
2026-05-21 23:27 ` [PATCH v3 2/4] Add wrappers for some Python APIs Tom Tromey
2026-05-21 23:27 ` [PATCH v3 3/4] Add wrappers for Python implementation functions and methods Tom Tromey
2026-05-21 23:27 ` [PATCH v3 4/4] Convert py-tui.c to the "python safety" approach Tom Tromey
2026-06-12 15:34 ` [PATCH v3 0/4] Python safety initial work Tom Tromey
2026-07-19 17:16 ` Tom Tromey
2026-07-21 11:45 ` Tom de Vries
2026-08-07 19:48 ` Tom Tromey [this message]
2026-08-09 8:02 ` Tom de Vries
2026-08-07 21:33 ` 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=87ldahyano.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=tdevries@suse.de \
/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