public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed 1/3] [gdb/testsuite] Fix gdb.btrace/reconnect.exp for remote target
Date: Tue, 28 Mar 2023 22:15:46 +0200	[thread overview]
Message-ID: <20230328201548.3452-1-tdevries@suse.de> (raw)

Fix test-case gdb.btrace/reconnect.exp for target board
remote-gdbserver-on-localhost using gdb_remote_download.

Tested on x86_64-linux.
---
 gdb/testsuite/gdb.btrace/reconnect.exp | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/gdb/testsuite/gdb.btrace/reconnect.exp b/gdb/testsuite/gdb.btrace/reconnect.exp
index 2c8358327a4..0365b054204 100644
--- a/gdb/testsuite/gdb.btrace/reconnect.exp
+++ b/gdb/testsuite/gdb.btrace/reconnect.exp
@@ -27,6 +27,8 @@ if [prepare_for_testing "failed to prepare" $testfile $srcfile] {
     return -1
 }
 
+set target_binfile [gdb_remote_download target $binfile]
+
 # Make sure we're disconnected and no recording is active, in case
 # we're testing with an extended-remote board, therefore already
 # connected.
@@ -37,7 +39,7 @@ with_test_prefix "preparation" {
 
 # Start fresh gdbserver.
 set gdbserver_reconnect_p 1
-set res [gdbserver_start "" $binfile]
+set res [gdbserver_start "" $target_binfile]
 set gdbserver_protocol [lindex $res 0]
 set gdbserver_gdbport [lindex $res 1]
 gdb_target_cmd $gdbserver_protocol $gdbserver_gdbport

base-commit: 4516ff910bb256b629c72cc5cf3535607296e42d
-- 
2.35.3


             reply	other threads:[~2023-03-28 20:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-28 20:15 Tom de Vries [this message]
2023-03-28 20:15 ` [pushed 2/3] [gdb/testsuite] Fix gdb.btrace/gcore.exp for remote host Tom de Vries
2023-03-28 20:15 ` [pushed 3/3] [gdb/testsuite] Fix gdb.btrace/multi-inferior.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=20230328201548.3452-1-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).