From: Tom de Vries <tdevries@suse.de>
To: gdb-patches@sourceware.org
Subject: [pushed] [gdb/testsuite] Fix gdb.base/fork-no-detach-follow-child-dlopen.exp for remote target
Date: Tue, 7 Mar 2023 15:29:04 +0100 [thread overview]
Message-ID: <20230307142904.11190-1-tdevries@suse.de> (raw)
Fix test-case gdb.base/fork-no-detach-follow-child-dlopen.exp for target board
remote-gdbserver-on-localhost.exp by using gdb_download_shlib and gdb_locate_shlib.
Tested on x86_64-linux.
---
.../gdb.base/fork-no-detach-follow-child-dlopen.exp | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/gdb/testsuite/gdb.base/fork-no-detach-follow-child-dlopen.exp b/gdb/testsuite/gdb.base/fork-no-detach-follow-child-dlopen.exp
index 6bc734ebf0f..94111fe3beb 100644
--- a/gdb/testsuite/gdb.base/fork-no-detach-follow-child-dlopen.exp
+++ b/gdb/testsuite/gdb.base/fork-no-detach-follow-child-dlopen.exp
@@ -32,14 +32,16 @@ if { [gdb_compile_shlib $srcdir/$subdir/$srcfile2 $shlib_path {debug}] != "" } {
return
}
-set opts [list shlib_load additional_flags=-DSHLIB_PATH="${shlib_path}"]
+set shlib_path_target [gdb_download_shlib $::shlib_path]
+
+set opts [list shlib_load additional_flags=-DSHLIB_PATH="${shlib_path_target}"]
if { [build_executable "failed to prepare" ${testfile} ${srcfile} $opts] } {
return
}
proc do_test {} {
clean_restart $::binfile
- gdb_load_shlib $::shlib_path
+ gdb_locate_shlib $::shlib_path
gdb_test_no_output "set follow-fork-mode child"
gdb_test_no_output "set detach-on-fork off"
base-commit: da4cc0cc3674024eaf51e6f98fef9fc6e558426a
--
2.35.3
reply other threads:[~2023-03-07 14:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20230307142904.11190-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).