From: Patrick Monnerat via Gdb-patches <gdb-patches@sourceware.org>
To: gdb-patches@sourceware.org
Subject: [PATCH] Notify observer of breakpoint auto-disabling
Date: Sun, 15 Aug 2021 02:33:08 +0200 [thread overview]
Message-ID: <20210815003308.10218-1-patrick@monnerat.net> (raw)
As breakpoint_modified observer is currently notified upon breakpoint stop
before handling auto-disabling when enable count is reached, the observer is
never notified of the disabling.
The problem affects:
- The MI interpreter enabled= value when reporting =breakpoint-modified
- A Python event handler for breakpoint_modified using the "enabled"
member of its parameter
- insight: breakpoint GUI window is not properly updated upon auto-disable
This patch moves the observer notification after the auto-disabling
code and implements corresponding tests for the MI and Python cases.
Fixes https://sourceware.org/bugzilla/show_bug.cgi?id=23336
---
gdb/breakpoint.c | 2 +-
.../gdb.mi/mi-breakpoint-changed.exp | 41 +++++++++++++++++++
gdb/testsuite/gdb.python/py-breakpoint.exp | 21 ++++++++++
3 files changed, 63 insertions(+), 1 deletion(-)
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 89af44ee4c6..feca224ccf4 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -5491,7 +5491,6 @@ bpstat_stop_status (const address_space *aspace,
if (bs->stop)
{
++(b->hit_count);
- gdb::observers::breakpoint_modified.notify (b);
/* We will stop here. */
if (b->disposition == disp_disable)
@@ -5501,6 +5500,7 @@ bpstat_stop_status (const address_space *aspace,
b->enable_state = bp_disabled;
removed_any = 1;
}
+ gdb::observers::breakpoint_modified.notify (b);
if (b->silent)
bs->print = 0;
bs->commands = b->commands;
diff --git a/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp b/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp
index 3f7ef8a79b6..0b814443b06 100644
--- a/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp
+++ b/gdb/testsuite/gdb.mi/mi-breakpoint-changed.exp
@@ -257,3 +257,44 @@ proc test_pending_resolved { } {
with_test_prefix "test_pending_resolved" {
test_pending_resolved
}
+
+# Test auto-disable is effective when notifying breakpoint-modified.
+
+proc test_auto_disable { } {
+ global mi_gdb_prompt
+ global lib_sl1 lib_sl2
+ global binfile
+
+ mi_clean_restart $binfile
+
+ mi_load_shlibs $lib_sl1 $lib_sl2
+
+ mi_runto_main
+
+ # Set the breakpoint.
+ mi_gdb_test "-break-insert -f pendfunc1" \
+ {(&.*)*.*~"Breakpoint 2 at.*\\n".*=breakpoint-created,bkpt=\{number="2",type="breakpoint".*\}.*\n\^done}
+
+ # Enable for one shot only.
+ mi_gdb_test "-break-enable count 1 2" \
+ {=breakpoint-modified,bkpt=\{number="2",type="breakpoint",disp="dis",enabled="y".*\}.*\n\^done}
+
+ mi_send_resuming_command "exec-continue" "continuing execution to breakpoint"
+
+ set test "breakpoint auto-disabling after enable count reached"
+ gdb_expect {
+ -re ".*=breakpoint-modified,bkpt=\{number=\"2\".*enabled=\"n\"" {
+ pass $test
+ }
+ -re ".*${mi_gdb_prompt}$" {
+ fail $test
+ }
+ timeout {
+ fail "$test (timeout)"
+ }
+ }
+}
+
+with_test_prefix "test_auto_disable" {
+ test_auto_disable
+}
diff --git a/gdb/testsuite/gdb.python/py-breakpoint.exp b/gdb/testsuite/gdb.python/py-breakpoint.exp
index e2ffe8cbe46..e9102e7e3ea 100644
--- a/gdb/testsuite/gdb.python/py-breakpoint.exp
+++ b/gdb/testsuite/gdb.python/py-breakpoint.exp
@@ -799,6 +799,26 @@ proc_with_prefix test_catchpoints {} {
gdb_test "continue" "Stopped at catchpoint event: ${num}"
}
+proc_with_prefix test_bkpt_auto_disable { } {
+ global srcfile testfile hex decimal
+
+ # Start with a fresh gdb.
+ clean_restart ${testfile}
+
+ if ![runto_main] then {
+ fail "cannot run to main."
+ return 0
+ }
+ delete_breakpoints
+
+ set mult_line [gdb_get_line_number "Break at multiply."]
+ gdb_breakpoint ${mult_line}
+ gdb_test "enable count 1 2" "" "One shot enable."
+ gdb_test "python gdb.events.breakpoint_modified.connect(lambda bp: print(bp.enabled))" \
+ "" "Trap breakpoint_modified event"
+ gdb_test "continue" "False.*" "auto-disabling after enable count reached"
+}
+
test_bkpt_basic
test_bkpt_deletion
test_bkpt_cond_and_cmds
@@ -815,3 +835,4 @@ test_bkpt_events
test_bkpt_explicit_loc
test_bkpt_qualified
test_bkpt_probe
+test_bkpt_auto_disable
--
2.31.1
next reply other threads:[~2021-08-15 0:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-15 0:33 Patrick Monnerat via Gdb-patches [this message]
2021-08-16 1:32 ` Simon Marchi via Gdb-patches
-- strict thread matches above, loose matches on Subject: below --
2021-08-16 12:44 Patrick Monnerat via Gdb-patches
2021-08-16 14:04 ` Simon Marchi via Gdb-patches
2021-08-16 14:09 ` Patrick Monnerat via Gdb-patches
2021-08-16 15:10 ` Simon Marchi via Gdb-patches
2021-08-16 16:18 ` Patrick Monnerat via Gdb-patches
2021-08-13 22:24 Patrick Monnerat via Gdb-patches
2021-08-14 4:05 ` Simon Marchi via Gdb-patches
2021-08-15 0:30 ` Patrick Monnerat via Gdb-patches
2021-08-13 15:31 Patrick Monnerat via Gdb-patches
2021-08-13 15:45 ` Simon Marchi via Gdb-patches
2021-08-13 16:27 ` Patrick Monnerat via Gdb-patches
2021-08-13 18:59 ` Simon Marchi via Gdb-patches
2021-08-13 22:15 ` Patrick Monnerat via Gdb-patches
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=20210815003308.10218-1-patrick@monnerat.net \
--to=gdb-patches@sourceware.org \
--cc=patrick@monnerat.net \
/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