aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2026-04-29 09:33:56 +0200
committerTankut Baris Aktemur <tankut.baris.aktemur@intel.com>2026-04-29 09:34:34 +0200
commit8a5e138e6276ce7644ab858751440cb59f35623b (patch)
treedb74c403a3b51f5a50a1bc7ce370d481679efce6
parent237eed6d652aa1b341c913d37142d060eb9481c4 (diff)
downloadbinutils-8a5e138e6276ce7644ab858751440cb59f35623b.tar.gz
binutils-8a5e138e6276ce7644ab858751440cb59f35623b.tar.bz2
binutils-8a5e138e6276ce7644ab858751440cb59f35623b.zip
gdb, testsuite: fix gdb.base/save-history.exp for native-extended-gdbserver
When executed with the native-extended-gdbserver board file, we get FAIL: gdb.base/save-history.exp: check history contents This is because the history file contains an extra line for the command 'target extended-remote ...'. Address this in the test. Approved-By: Tom Tromey <tom@tromey.com>
-rw-r--r--gdb/testsuite/gdb.base/save-history.exp7
1 files changed, 7 insertions, 0 deletions
diff --git a/gdb/testsuite/gdb.base/save-history.exp b/gdb/testsuite/gdb.base/save-history.exp
index a24b0b9454c..4b8eafa9ffa 100644
--- a/gdb/testsuite/gdb.base/save-history.exp
+++ b/gdb/testsuite/gdb.base/save-history.exp
@@ -30,6 +30,13 @@ gdb_test_no_output "save history $filename" \
set expected "set height 0\n"
append expected "set width 0\n"
+
+# There is an additional target connection command with the
+# extended-remote board file.
+if {[target_info gdb_protocol] == "extended-remote"} {
+ append expected "target extended-remote $gdbserver_gdbport\n"
+}
+
append expected "print 23\n"
append expected "save history $filename\n"