aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorCarl Love <cel@us.ibm.com>2021-07-20 18:08:15 -0500
committerCarl Love <cel@us.ibm.com>2021-07-23 10:34:42 -0500
commit27df69020ad14b8d8d710aaf635bbea467f5b4f0 (patch)
treecb5c2948e6744572732236faa3bdb9ebec042e7a
parent44710bb280e0cbb1d42367f82b35e095e9cded4b (diff)
downloadgdb-27df69020ad14b8d8d710aaf635bbea467f5b4f0.zip
gdb-27df69020ad14b8d8d710aaf635bbea467f5b4f0.tar.gz
gdb-27df69020ad14b8d8d710aaf635bbea467f5b4f0.tar.bz2
Fix for gdb.python/py-breakpoint.exp
Not all systems have hardware breakpoint support. Add a check to see if the system supports hardware breakpoints. gdb/testsuite/ChangeLog * gdb.python/py-breakpoint.exp (test_hardware_breakpoints): Add check for hardware breakpoint support.
-rw-r--r--gdb/testsuite/gdb.python/py-breakpoint.exp3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.python/py-breakpoint.exp b/gdb/testsuite/gdb.python/py-breakpoint.exp
index d8fb85b..e2ffe8c 100644
--- a/gdb/testsuite/gdb.python/py-breakpoint.exp
+++ b/gdb/testsuite/gdb.python/py-breakpoint.exp
@@ -255,6 +255,9 @@ proc_with_prefix test_bkpt_invisible { } {
proc_with_prefix test_hardware_breakpoints { } {
global srcfile testfile hex decimal
+ # Skip these tests if the HW does not support hardware breakpoints.
+ if { [skip_hw_breakpoint_tests] } { return 0 }
+
# Start with a fresh gdb.
clean_restart ${testfile}