Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Tomáš Hrnčiar" <thrnciar@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gdb/python: add allow_pending parameter to gdb.Breakpoint constructor
Date: Tue, 13 Oct 2026 15:55:28 +0300	[thread overview]
Message-ID: <86jynlg3pb.fsf@gnu.org> (raw)
In-Reply-To: <20261013074751.754142-1-thrnciar@redhat.com> (message from =?utf-8?B?VG9tw6HFoQlIcm7EjWlhcg==?= on Tue, 13 Oct 2026 09:47:50 +0200)

> From: Tomáš Hrnčiar <thrnciar@redhat.com>
> Cc: Tomáš Hrnčiar <thrnciar@redhat.com>
> Date: Tue, 13 Oct 2026 09:47:50 +0200
> 
> 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.
> ---
>  gdb/NEWS                                   |  6 ++
>  gdb/doc/python.texi                        | 17 +++--
>  gdb/python/py-breakpoint.c                 | 16 +++--
>  gdb/testsuite/gdb.python/py-breakpoint.exp | 82 ++++++++++++++++++++--
>  4 files changed, 109 insertions(+), 12 deletions(-)

Thanks, the documentation parts are okay.

Reviewed-By: Eli Zaretskii <eliz@gnu.org>

  reply	other threads:[~2026-10-13 12:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  7:47 Tomáš Hrnčiar
2026-10-13 12:55 ` Eli Zaretskii [this message]
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

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=86jynlg3pb.fsf@gnu.org \
    --to=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