public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "kevin.pouget at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/12816] New: No 'pending' support for breakpoints created from Python
Date: Fri, 27 May 2011 08:57:00 -0000 [thread overview]
Message-ID: <bug-12816-4717@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=12816
Summary: No 'pending' support for breakpoints created from
Python
Product: gdb
Version: HEAD
Status: NEW
Severity: enhancement
Priority: P2
Component: python
AssignedTo: unassigned@sourceware.org
ReportedBy: kevin.pouget@gmail.com
when one creates a gdb.Breakpoint object, s/he has no control on its pending
state:
> (gdb) python gdb.Breakpoint('send')
> No symbol table is loaded. Use the "file" command.
> Breakpoint 4 (send) pending.
it would be convenient to
1) specify if we allow or not the breakpoint to be pending
2) remove the two lines written by GDB
3) know whether the breakpoint has actually been set or is pending
(I should provide a solution for 3 soon)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2011-05-27 8:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-27 8:57 kevin.pouget at gmail dot com [this message]
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
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@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).