From: Tom Tromey <tromey@adacore.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@adacore.com>
Subject: [PATCH 1/2] Don't let .gdb_history file cause failures
Date: Mon, 23 Jan 2023 15:02:56 -0700 [thread overview]
Message-ID: <20230123220257.3773828-2-tromey@adacore.com> (raw)
In-Reply-To: <20230123220257.3773828-1-tromey@adacore.com>
I had a .gdb_history file in my testsuite directory in the build tree,
and this provoked a failure in gdbhistsize-history.exp. It seems
simple to prevent this file from causing a failure.
---
gdb/testsuite/gdb.base/gdbhistsize-history.exp | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/gdb/testsuite/gdb.base/gdbhistsize-history.exp b/gdb/testsuite/gdb.base/gdbhistsize-history.exp
index d3e4a052c6b..f4bf11a10be 100644
--- a/gdb/testsuite/gdb.base/gdbhistsize-history.exp
+++ b/gdb/testsuite/gdb.base/gdbhistsize-history.exp
@@ -39,6 +39,10 @@ proc test_histsize_history_setting { histsize size { env_var "GDBHISTSIZE" } } {
unset -nocomplain env(GDBHISTFILE)
unset -nocomplain env(GDBHISTSIZE)
+ # Ensure we don't accidentally pick up a .gdb_history from the
+ # testsuite directory.
+ set env(GDBHISTFILE) [standard_output_file .gdb_history]
+
set env($env_var) $histsize
with_test_prefix "histsize=$histsize" {
--
2.38.1
next prev parent reply other threads:[~2023-01-23 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 22:02 [PATCH 0/2] Suppress some FAILs Tom Tromey
2023-01-23 22:02 ` Tom Tromey [this message]
2023-01-23 22:02 ` [PATCH 2/2] Avoid FAILs in gdb.compile Tom Tromey
2023-01-24 15:41 ` Alexandra Petlanova Hajkova
2023-02-08 17:18 ` [PATCH 0/2] Suppress some FAILs Tom Tromey
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=20230123220257.3773828-2-tromey@adacore.com \
--to=tromey@adacore.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).