From: Tom Tromey <tom@tromey.com>
To: "Tomáš Hrnčiar" <thrnciar@redhat.com>
Cc: gdb-patches@sourceware.org, tom@tromey.com, Eli Zaretskii <eliz@gnu.org>
Subject: Re: [PATCH v2] gdb/python: add allow_pending parameter to gdb.Breakpoint constructor
Date: Tue, 27 Oct 2026 08:06:47 -0600 [thread overview]
Message-ID: <87v76np79k.fsf@tromey.com> (raw)
In-Reply-To: <20261027080921.2944156-1-thrnciar@redhat.com> (=?utf-8?B?IlRvbcOhxaEgSHJuxI1pYXIiJ3M=?= message of "Tue, 27 Oct 2026 09:09:21 +0100")
>>>>> Tomáš Hrnčiar <thrnciar@redhat.com> writes:
> Add a new allow_pending parameter to the gdb.Breakpoint constructor.
> Setting the new parameter to False causes GDB to raise an error instead
> of creating a pending breakpoint. By default this parameter is True,
> which allows pending breakpoints to be created, preserving the existing
> behaviour.
> Reviewed-By: Eli Zaretskii <eliz@gnu.org>
> Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=12816
Ok. Thank you.
Approved-By: Tom Tromey <tom@tromey.com>
Tom
prev parent reply other threads:[~2026-10-27 14:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 7:47 [PATCH] " Tomáš Hrnčiar
2026-10-13 12:55 ` Eli Zaretskii
2026-10-14 15:58 ` Tom Tromey
2026-10-22 13:54 ` Andrew Burgess
2026-10-22 17:50 ` Simon Marchi
2026-10-22 18:35 ` Tom Tromey
2026-10-27 8:09 ` [PATCH v2] " Tomáš Hrnčiar
2026-10-27 14:06 ` Tom Tromey [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=87v76np79k.fsf@tromey.com \
--to=tom@tromey.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thrnciar@redhat.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