Skip watch_thread_num.exp on targets without access watchpoints

Since watch_thread_num.exp was changed to use access watchpoints, the
test case fails on s390 and s390x, since those targets do not support
access watchpoints.  This patch skips the test case on such targets.

gdb/testsuite/ChangeLog:

	* gdb.base/watch_thread_num.exp: Skip test on targets without
	access watchpoints.

diff --git a/gdb/testsuite/ChangeLog b/gdb/testsuite/ChangeLog
index a2bb3c92ef36b388a43f5387620e4d940e50d5b1..8284a496a6934ab06d3cb2c82e29dafb87192f7a 100644 (file)
--- a/gdb/testsuite/ChangeLog
+++ b/gdb/testsuite/ChangeLog
@@ -1,3 +1,8 @@
+2015-05-08  Andreas Arnez  <arnez@linux.vnet.ibm.com>
+
+       * gdb.base/watch_thread_num.exp: Skip test on targets without
+       access watchpoints.
+
 2015-05-06  Pedro Alves  <palves@redhat.com>
 
        PR server/18081

diff --git a/gdb/testsuite/gdb.base/watch_thread_num.exp b/gdb/testsuite/gdb.base/watch_thread_num.exp
index d559f22386fb561570785fbb027bf23199571e1d..6d767c273409e53a8305912271535bd91da5bc90 100644 (file)
--- a/gdb/testsuite/gdb.base/watch_thread_num.exp
+++ b/gdb/testsuite/gdb.base/watch_thread_num.exp
@@ -21,7 +21,9 @@
 
 # This test verifies that a watchpoint is detected in the proper thread
 # so the test is only meaningful on a system with hardware watchpoints.
-if {[skip_hw_watchpoint_tests]} {
+# More specifically, the implementation of this test uses access
+# watchpoints, so skip it when those are not available.
+if {[skip_hw_watchpoint_access_tests]} {
     return 0
 }