From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed 4/6] [gdb/testsuite] Fix gdb.guile/scm-objfile-script.exp for remote host
Date: Wed, 29 Mar 2023 08:02:02 +0200 [thread overview]
Message-ID: <20230329060204.32690-4-tdevries@suse.de> (raw)
In-Reply-To: <20230329060204.32690-1-tdevries@suse.de>
Fix test-case gdb.guile/scm-objfile-script.exp using gdb_remote_download.
Tested on x86_64-linux.
---
gdb/testsuite/gdb.guile/scm-objfile-script.exp | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.guile/scm-objfile-script.exp b/gdb/testsuite/gdb.guile/scm-objfile-script.exp
index dc390b6b9ec..89abc38ed3c 100644
--- a/gdb/testsuite/gdb.guile/scm-objfile-script.exp
+++ b/gdb/testsuite/gdb.guile/scm-objfile-script.exp
@@ -29,9 +29,9 @@ if {[build_executable $testfile.exp $testfile $srcfile debug] == -1} {
# Make the -gdb.scm script available to gdb, it is automagically loaded by gdb.
# Care is taken to put it in the same directory as the binary so that
# gdb will find it.
-set remote_guile_file [remote_download host \
+set remote_guile_file [gdb_remote_download host \
${srcdir}/${subdir}/${testfile}-gdb.in \
- [host_standard_output_file ${testfile}-gdb.scm]]
+ ${testfile}-gdb.scm]
clean_restart
gdb_test_no_output "set auto-load safe-path ${remote_guile_file}" \
--
2.35.3
next prev parent reply other threads:[~2023-03-29 6:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-29 6:01 [pushed 1/6] [gdb/testsuite] Fix gdb.guile/guile.exp " Tom de Vries
2023-03-29 6:02 ` [pushed 2/6] [gdb/testsuite] Fix gdb.guile/scm-cmd.exp without readline Tom de Vries
2023-03-29 6:02 ` [pushed 3/6] [gdb/testsuite] Fix gdb.guile/scm-objfile-script.exp for remote host Tom de Vries
2023-03-29 6:02 ` Tom de Vries [this message]
2023-03-29 6:02 ` [pushed 5/6] [gdb/testsuite] Fix /gdb.guile/scm-parameter.exp " Tom de Vries
2023-03-29 6:02 ` [pushed 6/6] [gdb/testsuite] Fix gdb.guile/scm-symbol.exp " Tom de Vries
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=20230329060204.32690-4-tdevries@suse.de \
--to=tdevries@suse.de \
--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).