From: Tom Tromey <tom@tromey.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tom@tromey.com>
Subject: [PATCH 0/5] Use Python safety API for breakpoint locations
Date: Wed, 14 Oct 2026 08:08:48 -0600 [thread overview]
Message-ID: <20261014-python-safety-breakpoint-v1-0-c8e72d58f3cd@tromey.com> (raw)
This series changes the breakpoint location code to use the Python
safety API.
Tested on x86-64 Fedora 40.
Signed-off-by: Tom Tromey <tom@tromey.com>
---
Tom Tromey (5):
Rewrite gdb.BreakpointLocation repr method
Move two macros from python-internal.h to py-breakpoint.c
Add require_valid to Python breakpoint and breakpoint location
Rewrite breakpoint location getter methods
Rewrite gdb.BreakpointLocation setter
gdb/python/py-breakpoint.c | 371 ++++++++++++++++++++++---------------------
gdb/python/py-ref.h | 7 +
gdb/python/py-wrappers.h | 10 ++
gdb/python/python-internal.h | 26 +--
4 files changed, 209 insertions(+), 205 deletions(-)
---
base-commit: 692a398424b5468c17843b68faefa26169d961a1
change-id: 20261014-python-safety-breakpoint-6f2868b31b69
Best regards,
--
Tom Tromey <tom@tromey.com>
next reply other threads:[~2026-10-14 14:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 14:08 Tom Tromey [this message]
2026-10-14 14:08 ` [PATCH 1/5] Rewrite gdb.BreakpointLocation repr method Tom Tromey
2026-10-14 14:08 ` [PATCH 2/5] Move two macros from python-internal.h to py-breakpoint.c Tom Tromey
2026-10-14 14:08 ` [PATCH 3/5] Add require_valid to Python breakpoint and breakpoint location Tom Tromey
2026-10-14 14:08 ` [PATCH 4/5] Rewrite breakpoint location getter methods Tom Tromey
2026-10-14 14:08 ` [PATCH 5/5] Rewrite gdb.BreakpointLocation setter 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=20261014-python-safety-breakpoint-v1-0-c8e72d58f3cd@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
/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