From: Tom de Vries <tdevries@suse.de>
Date: Tue, 3 Dec 2024 15:53:14 +0000 (+0100)
Subject: [gdb/testsuite] Fix gdb.base/reset-catchpoint-cond.exp with --with-expat=no
X-Git-Tag: gdb-16-branchpoint~206
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d556cf2ec79ed5afbbdd523484954c6a520b5b73;p=thirdparty%2Fbinutils-gdb.git

[gdb/testsuite] Fix gdb.base/reset-catchpoint-cond.exp with --with-expat=no

When building gdb with --with-expat=no and running test-case
gdb.base/reset-catchpoint-cond.exp we get:
...
(gdb) catch syscall write^M
warning: Can not parse XML syscalls information; \
  XML support was disabled at compile time.^M
Unknown syscall name 'write'.^M
(gdb) FAIL: $exp: mode=syscall: catch syscall write
...

Fix this by skipping the test for --with-expat=no.

Tested on x86_64-linux.
---

diff --git a/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp b/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp
index e119c32e702..dabacd47467 100644
--- a/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp
+++ b/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp
@@ -165,5 +165,8 @@ proc run_test { mode } {
 
 # Run the tests.
 foreach_with_prefix mode { syscall signal fork } {
+    if { $mode == "syscall" && ![allow_xml_test] } {
+	continue
+    }
     run_test $mode
 }