From: "Andrew Burgess" <aburgess@broadcom.com>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: [PATCH] Extra error message from update_watchpoint
Date: Fri, 18 Oct 2013 09:20:00 -0000 [thread overview]
Message-ID: <5260FD66.7090506@broadcom.com> (raw)
While working on this:
URL
I found the error message:
Expression cannot be implemented with read/access watchpoint.
is also issued when hardware watchpoints are turned off, this
error seems a little confusing as the problem is not the
expression, but that software read/access watchpoints is not
supported.
After the patch I've ADDED an extra error message:
Software read/access watchpoints not supported.
Which will be selected where appropriate.
OK to apply?
Thanks,
Andrew
gdb/ChangeLog
2013-10-18 Andrew Burgess <aburgess@broadcom.com>
* breakpoint.c (update_watchpoint): Give a different error message
when software watchpoints are explicitly turned off.
gdb/testsuite/ChangeLog
2013-10-18 Andrew Burgess <aburgess@broadcom.com>
* gdb.base/watchpoint.exp: (test_no_hw_watchpoints): Update
expected results, add additional test.
(test_watch_register_location): New.
(do_tests): Call test_watch_register_location.
diff --git a/gdb/breakpoint.c b/gdb/breakpoint.c
index c630b87..6e87e22 100644
--- a/gdb/breakpoint.c
+++ b/gdb/breakpoint.c
@@ -1946,8 +1946,13 @@ update_watchpoint (struct watchpoint *b, int reparse)
}
}
else if (!b->base.ops->works_in_software_mode (&b->base))
- error (_("Expression cannot be implemented with "
- "read/access watchpoint."));
+ {
+ if (!can_use_hw_watchpoints)
+ error (_("Software read/access watchpoints not supported."));
+ else
+ error (_("Expression cannot be implemented with "
+ "read/access watchpoint."));
+ }
else
b->base.type = bp_watchpoint;
diff --git a/gdb/testsuite/gdb.base/watchpoint.exp b/gdb/testsuite/gdb.base/watchpoint.exp
index e0d4f81..5a5f149 100644
--- a/gdb/testsuite/gdb.base/watchpoint.exp
+++ b/gdb/testsuite/gdb.base/watchpoint.exp
@@ -825,8 +825,12 @@ proc test_no_hw_watchpoints {} {
# refrains from using them.
#
gdb_test "rwatch ival3" \
- "Expression cannot be implemented with read/access watchpoint..*" \
+ "Software read/access watchpoints not supported..*" \
"rwatch disallowed when can-set-hw-watchpoints cleared"
+ gdb_test "awatch ival3" \
+ "Software read/access watchpoints not supported..*" \
+ "awatch disallowed when can-set-hw-watchpoints cleared"
+
# Re-enable hardware watchpoints if necessary.
if ![target_info exists gdb,no_hardware_watchpoints] {
@@ -879,6 +883,22 @@ proc test_watchpoint_in_big_blob {} {
gdb_test_no_output "delete \$bpnum" "delete watch buf"
}
+proc test_watch_register_location {} {
+ global no_hw
+
+ if {!$no_hw && ![target_info exists gdb,no_hardware_watchpoints]} {
+ # Non-memory read/access watchpoints are not supported, they would
+ # require software read/access watchpoint support (which is not
+ # currently available).
+ gdb_test "rwatch \$pc" \
+ "Expression cannot be implemented with read/access watchpoint..*" \
+ "rwatch disallowed for register based expression"
+ gdb_test "awatch \$pc" \
+ "Expression cannot be implemented with read/access watchpoint..*" \
+ "awatch disallowed for register based expression"
+ }
+}
+
# Start with a fresh gdb.
set prev_timeout $timeout
@@ -940,6 +960,8 @@ proc do_tests {} {
test_wide_location_1
test_wide_location_2
+
+ test_watch_register_location
}
# On targets that can do hardware watchpoints, run the tests twice:
next reply other threads:[~2013-10-18 9:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 9:20 Andrew Burgess [this message]
2013-10-18 17:18 ` Pedro Alves
2013-10-29 16:44 ` Andrew Burgess
2013-10-29 17:09 ` Pedro Alves
2013-10-29 17:19 ` Eli Zaretskii
2013-10-29 17:38 ` Andrew Burgess
2013-10-29 17:52 ` Pedro Alves
2013-10-29 19:09 ` Eli Zaretskii
2013-10-30 11:49 ` Andrew Burgess
2013-10-30 15:41 ` Eli Zaretskii
2013-10-30 17:13 ` Andrew Burgess
2013-10-30 18:41 ` Eli Zaretskii
2013-10-31 13:05 ` Andrew Burgess
2013-10-30 18:48 ` Pedro Alves
2013-10-30 19:19 ` Eli Zaretskii
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=5260FD66.7090506@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