public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "andrew.burgess at embecosm dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug python/18655] Python FinishBreakpoints are not deleted
Date: Fri, 10 Jul 2015 18:52:00 -0000 [thread overview]
Message-ID: <bug-18655-4717-KWJccNfSk0@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-18655-4717@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=18655
Andrew Burgess <andrew.burgess at embecosm dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |andrew.burgess at embecosm dot com
--- Comment #3 from Andrew Burgess <andrew.burgess at embecosm dot com> ---
This old thread about the FinishBreakpoints might be of interest to anyone
taking on this bug: https://sourceware.org/ml/gdb-patches/2012-09/msg00436.html
I have not confirmed if those issues still all apply, apologies if they've been
fixed.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2015-07-10 18:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 15:43 [Bug python/18655] New: GDB " simon.marchi at ericsson dot com
2015-07-10 15:43 ` [Bug python/18655] " simon.marchi at ericsson dot com
2015-07-10 15:44 ` simon.marchi at ericsson dot com
2015-07-10 18:17 ` [Bug python/18655] " simon.marchi at ericsson dot com
2015-07-10 18:52 ` andrew.burgess at embecosm dot com [this message]
2022-09-17 0:19 ` j3.soon777 at gmail dot com
2022-09-17 0:24 ` j3.soon777 at gmail dot com
2022-09-20 17:35 ` j3.soon777 at gmail dot com
2022-11-18 15:56 ` cvs-commit at gcc dot gnu.org
2022-11-18 16:01 ` simark at simark dot ca
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-18655-4717-KWJccNfSk0@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).