From: "Andrew Burgess" <aburgess@broadcom.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PATCH] hardware watchpoints turned off, inferior not yet started
Date: Wed, 16 Oct 2013 09:39:00 -0000 [thread overview]
Message-ID: <525E5EB6.4070305@broadcom.com> (raw)
The following seems confusing to me:
$ gdb -q watch.x
Reading symbols from /some/path/to/watch.x...done.
(gdb) set can-use-hw-watchpoints 0
(gdb) watch -l my_var
Hardware watchpoint 1: -location my_var
(gdb)
Notice that despite turning hardware watchpoints off
the watchpoint created is reported to be a hardware
watchpoint. Once I actually start the inferior the
watchpoint is downgraded to a software watchpoint,
but still, this feels like it might cause confusion,
and is pretty easy to fix.
OK to apply?
Thanks,
Andrew
gdb/ChangeLog
2013-10-16 Andrew Burgess <aburgess@broadcom.com>
* breakpoint.c (update_watchpoint): Create software watchpoints if
the inferior has not yet started and hardware watchpoints are
turned off.
gdb/testsuite/ChangeLog
2013-10-16 Andrew Burgess <aburgess@broadcom.com>
* gdb.base/watchpoints.exp: Add test for setting software
watchpoint before starting the inferior.
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index 5ce50de..2902dc1 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -1800,6 +1800,8 @@ update_watchpoint (struct watchpoint *b, int reparse)
/* Without execution, memory can't change. No use to try and
set watchpoint locations. The watchpoint will be reset when
the target gains execution, through breakpoint_re_set. */
+ if (!can_use_hw_watchpoints)
+ b->base.type = bp_watchpoint;
}
else if (within_current_scope && b->exp)
{
diff --git a/gdb/testsuite/gdb.base/watchpoints.exp b/gdb/testsuite/gdb.base/watchpoints.exp
index 7c10d81..2442bcd 100644
--- a/gdb/testsuite/gdb.base/watchpoints.exp
+++ b/gdb/testsuite/gdb.base/watchpoints.exp
@@ -29,6 +29,17 @@ if {[prepare_for_testing $testfile.exp $testfile $srcfile debug]} {
return -1
}
+ # Ensure that if we turn off hardware watchpoints and set a watch point
+ # before starting the inferior the watchpoint created will not be a
+ # hardware watchpoint.
+ gdb_test_no_output "set can-use-hw-watchpoints 0" ""
+ gdb_test "watch ival1" "Watchpoint \[0-9\]+: ival1" \
+ "Set software watchpoint before starting the inferior"
+
+ # This will turn hardware watchpoints back on and delete the watchpoint
+ # we just created.
+ clean_restart ${binfile}
+
# Disable hardware watchpoints if necessary.
if [target_info exists gdb,no_hardware_watchpoints] {
gdb_test_no_output "set can-use-hw-watchpoints 0" ""
next reply other threads:[~2013-10-16 9:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-16 9:39 Andrew Burgess [this message]
2013-10-16 12:32 ` Pedro Alves
2013-10-16 15:43 ` Andrew Burgess
2013-10-16 16:28 ` Pedro Alves
2013-10-18 9:14 ` Andrew Burgess
2013-10-18 14:37 ` Andrew Burgess
2013-10-18 15:33 ` Pedro Alves
2013-10-18 16:26 ` Andrew Burgess
2013-10-18 15:26 ` Pedro Alves
2013-10-18 15:43 ` Andrew Burgess
2013-11-07 12:21 Jose E. Marchesi
2013-11-08 12:03 ` Pedro Alves
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=525E5EB6.4070305@broadcom.com \
--to=aburgess@broadcom.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