public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simark at simark dot ca" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12816] No 'pending' support for breakpoints created from Python
Date: Tue, 04 Jan 2022 14:43:23 +0000	[thread overview]
Message-ID: <bug-12816-4717-eQ7dvrCge0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12816-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12816

Simon Marchi <simark at simark dot ca> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |simark at simark dot ca

--- Comment #3 from Simon Marchi <simark at simark dot ca> ---
(In reply to Hannes Domani from comment #2)
> Since gdb 7.12, gdb.Breakpoint has the (read-only) "pending" attribute.
> Is more needed to resolve this ticket?

AFAIU, it doesn't.  This bug is about being able to decide whether to allow
pending breakpoints when creating a gdb.Breakpoint.  I would imagine a
parameter like:

  gdb.Breakpoint("my_function", allow_pending=True)

for example.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-01-04 14:43 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-27  8:57 [Bug python/12816] New: " kevin.pouget at gmail dot com
2011-12-08 13:56 ` [Bug python/12816] " kevin.pouget at gmail dot com
2011-12-08 13:57 ` kevin.pouget at gmail dot com
2022-01-03 15:13 ` ssbssa at sourceware dot org
2022-01-04 14:43 ` simark at simark dot ca [this message]
2022-06-05 14:54 ` tromey at sourceware dot org
2022-12-07 15:53 ` tromey at sourceware dot org
2022-12-08 18:39 ` tromey at sourceware dot org
2022-12-21 20:21 ` tromey at sourceware dot org
2024-03-12 14:08 ` tromey at sourceware dot org

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=bug-12816-4717-eQ7dvrCge0@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).