From: Tankut Baris Aktemur <tankut.baris.aktemur@intel.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] gdb, testsuite: fix gdb.base/save-history.exp for native-extended-gdbserver
Date: Fri, 17 Apr 2026 12:35:43 +0200 [thread overview]
Message-ID: <20260417103543.2135788-1-tankut.baris.aktemur@intel.com> (raw)
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 ...'. To keep the test
straightforward, skip it if using the extended-remote target.
---
gdb/testsuite/gdb.base/save-history.exp | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/gdb/testsuite/gdb.base/save-history.exp b/gdb/testsuite/gdb.base/save-history.exp
index bb7a56b2a72..5ca47f3bc1f 100644
--- a/gdb/testsuite/gdb.base/save-history.exp
+++ b/gdb/testsuite/gdb.base/save-history.exp
@@ -19,6 +19,13 @@
require {!is_remote host}
+# A remote server adds extra setup commands in history. To keep the
+# test straighforward, skip extended-remote target.
+if {[target_info gdb_protocol] == "extended-remote"} {
+ unsupported "test not aimed for extended-remote target"
+ return
+}
+
gdb_start
# Get something in history.
--
2.34.1
Intel Deutschland GmbH
Registered Address: Dornacher Strasse 1, 85622 Feldkirchen, Germany
Tel: +49 89 991 430, www.intel.de
Managing Directors: Harry Demas, Jeffrey Schneiderman, Yin Chong Sorrell
Chairperson of the Supervisory Board: Nicole Lau
Registered Seat: Munich
Commercial Register: Amtsgericht Muenchen HRB 186928
next reply other threads:[~2026-04-17 10:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-17 10:35 Tankut Baris Aktemur [this message]
2026-04-17 12:54 ` Guinevere Larsen
2026-04-17 13:33 ` Aktemur, Tankut Baris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260417103543.2135788-1-tankut.baris.aktemur@intel.com \
--to=tankut.baris.aktemur@intel.com \
--cc=gdb-patches@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox