aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom de Vries <tdevries@suse.de>2024-12-03 16:53:14 +0100
committerTom de Vries <tdevries@suse.de>2024-12-03 16:53:14 +0100
commitd556cf2ec79ed5afbbdd523484954c6a520b5b73 (patch)
tree985e968373d9244d0a3bd9cede9e653df3acc76e
parent6804a0969d4a27870e76e472d0e5b66a7c4c9dc9 (diff)
downloadbinutils-d556cf2ec79ed5afbbdd523484954c6a520b5b73.zip
binutils-d556cf2ec79ed5afbbdd523484954c6a520b5b73.tar.gz
binutils-d556cf2ec79ed5afbbdd523484954c6a520b5b73.tar.bz2
[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.
-rw-r--r--gdb/testsuite/gdb.base/reset-catchpoint-cond.exp3
1 files changed, 3 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp b/gdb/testsuite/gdb.base/reset-catchpoint-cond.exp
index e119c32..dabacd4 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
}