From: Johnson Sun <j3.soon777@gmail.com>
To: gdb-patches@sourceware.org
Cc: j3.soon777@gmail.com
Subject: [PATCH 0/3] [PR gdb/18655] Fix Python FinishBreakpoints not deleted bug
Date: Wed, 21 Sep 2022 01:24:24 +0800 [thread overview]
Message-ID: <20220920172426.90659-1-j3.soon777@gmail.com> (raw)
This adds tests and fixes Bug 18655: Python FinishBreakpoints are not deleted.
Patch #1 adds a testcase.
Patch #2 is the core of the fix.
Patch #3 fixes some comments.
I ran the testsuite on an x86_64 Ubuntu 22.04 VM and find no test regression.
Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=18655
gdb/python/py-finishbreakpoint.c | 5 ++-
.../gdb.python/py-finish-breakpoint-deletion.c | 28 +++++++++++++
.../gdb.python/py-finish-breakpoint-deletion.exp | 46 ++++++++++++++++++++++
.../gdb.python/py-finish-breakpoint-deletion.py | 33 ++++++++++++++++
4 files changed, 110 insertions(+), 2 deletions(-)
base-commit: c99b2113a478a075e8d8f7c3848a92f1ce73f847
next reply other threads:[~2022-09-20 17:28 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 17:24 Johnson Sun [this message]
2022-09-20 17:24 ` [PATCH 1/3] [gdb/testsuite] Add gdb.python/py-finish-breakpoint-deletion.exp for Bug 18655 Johnson Sun
2022-09-21 13:44 ` Bruno Larsen
2022-09-23 5:16 ` Johnson Sun
2022-09-20 17:24 ` [PATCH 2/3] [gdb/python] Fix " Johnson Sun
2022-09-21 14:02 ` Bruno Larsen
2022-09-20 17:24 ` [PATCH 3/3] [gdb/python] Replace gdbpy_should_stop with gdbpy_breakpoint_cond_says_stop Johnson Sun
2022-09-21 14:09 ` Bruno Larsen
2022-09-23 5:41 ` [PATCH v2] [PR python/18655] Fix deletion of FinishBreakpoints Johnson Sun
2022-09-23 8:32 ` Bruno Larsen
2022-09-23 20:16 ` Johnson Sun
2022-09-23 20:27 ` [PATCH v3] " Johnson Sun
2022-10-12 1:53 ` Simon Marchi
2022-10-20 17:34 ` Johnson Sun
2022-10-20 17:49 ` [PATCH v4] " Johnson Sun
2022-11-18 12:16 ` [PING] " Johnson Sun
2022-11-18 15:56 ` Simon Marchi
2022-09-23 6:00 ` [PATCH v2] [gdb/python] Replace gdbpy_should_stop with gdbpy_breakpoint_cond_says_stop Johnson Sun
2022-10-20 18:24 ` [PING] " Johnson Sun
2022-11-18 12:14 ` [PING^2] " Johnson Sun
2022-11-25 15:10 ` [PING^3] " Johnson Sun
2022-12-04 16:45 ` [PING^4] " Johnson Sun
2022-12-12 21:44 ` [PING^5] " Johnson Sun
2022-12-13 2:34 ` Simon Marchi
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=20220920172426.90659-1-j3.soon777@gmail.com \
--to=j3.soon777@gmail.com \
--cc=gdb-patches@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).