diff options
| author | Tom de Vries <tdevries@suse.de> | 2025-01-08 10:06:28 +0100 |
|---|---|---|
| committer | Tom de Vries <tdevries@suse.de> | 2025-01-08 10:06:28 +0100 |
| commit | 19ca41656eef546957d707aa086ab196f0890c51 (patch) | |
| tree | 0aee4e1b25d9ef8ec5d2d62a78db0dd3ea3955eb /gdb/testsuite | |
| parent | 8520cebeb576ae345ae506f2d7207668cc68d1cb (diff) | |
| download | gdb-19ca41656eef546957d707aa086ab196f0890c51.zip gdb-19ca41656eef546957d707aa086ab196f0890c51.tar.gz gdb-19ca41656eef546957d707aa086ab196f0890c51.tar.bz2 | |
[gdb/testsuite] Fix gdb.base/reset-catchpoint-cond.exp for !supports_catch_syscall
I ran test-case gdb.base/reset-catchpoint-cond.exp on riscv64-linux, and got:
...
(gdb) catch syscall write^M
The feature 'catch syscall' is not supported on this architecture yet.^M
(gdb) FAIL: $exp: mode=syscall: catch syscall write
...
Fix this by checking for supports_catch_syscall.
Tested on riscv64-linux and x86_64-linux.
Diffstat (limited to 'gdb/testsuite')
| -rw-r--r-- | gdb/testsuite/gdb.base/reset-catchpoint-cond.exp | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp b/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp index dabacd4..d953938 100644 --- a/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp +++ b/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp @@ -165,7 +165,8 @@ proc run_test { mode } { # Run the tests. foreach_with_prefix mode { syscall signal fork } { - if { $mode == "syscall" && ![allow_xml_test] } { + if { $mode == "syscall" + && ( ![allow_xml_test] || ![supports_catch_syscall] ) } { continue } run_test $mode |