From: Tom de Vries <tdevries@suse.de>
Date: Wed, 8 Jan 2025 09:06:28 +0000 (+0100)
Subject: [gdb/testsuite] Fix gdb.base/reset-catchpoint-cond.exp for !supports_catch_syscall
X-Git-Tag: binutils-2_44~235
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=19ca41656eef546957d707aa086ab196f0890c51;p=thirdparty%2Fbinutils-gdb.git

[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.
---

diff --git a/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp b/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp
index dabacd47467..d9539383c95 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