From: Ivan Tetyushkin <ivan.tetyushkin@syntacore.com>
To: gdb-patches@sourceware.org
Cc: Ivan Tetyushkin <ivan.tetyushkin@syntacore.com>
Subject: [PATCH 2/7] [gdb/testsuite] fix test gdb.base/print-file-var.exp for remote execution
Date: Tue, 25 Oct 2022 19:29:44 +0300 [thread overview]
Message-ID: <20221025162946.727169-3-ivan.tetyushkin@syntacore.com> (raw)
In-Reply-To: <20221025162946.727169-1-ivan.tetyushkin@syntacore.com>
---
gdb/testsuite/gdb.base/print-file-var.exp | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/gdb/testsuite/gdb.base/print-file-var.exp b/gdb/testsuite/gdb.base/print-file-var.exp
index 9abe87d7758..73137630fed 100644
--- a/gdb/testsuite/gdb.base/print-file-var.exp
+++ b/gdb/testsuite/gdb.base/print-file-var.exp
@@ -42,6 +42,8 @@ proc test {hidden dlopen version_id_main lang} {
set libobj1 [standard_output_file ${lib1}$suffix.so]
set libobj2 [standard_output_file ${lib2}$suffix.so]
+ set runtimelibobj2 [get_runtime_file $libobj2]
+
set lib_opts { debug $lang }
lappend lib_opts "additional_flags=-DHIDDEN=$hidden"
@@ -60,7 +62,7 @@ proc test {hidden dlopen version_id_main lang} {
set link_opts [list debug shlib=${libobj1}]
if {$dlopen} {
- lappend main_opts "additional_flags=-DSHLIB_NAME=\"$libobj2\""
+ lappend main_opts "additional_flags=-DSHLIB_NAME=\"$runtimelibobj2\""
lappend link_opts "shlib_load"
} else {
lappend link_opts "shlib=${libobj2}"
--
2.38.1
next prev parent reply other threads:[~2022-10-25 16:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 16:29 [PATCH 0/7] introduce get_runtime_path Ivan Tetyushkin
2022-10-25 16:29 ` [PATCH 1/7] [gdb/testsuite] Adding function to find runtime path to support remote execution for testsuite Ivan Tetyushkin
2022-10-25 16:29 ` Ivan Tetyushkin [this message]
2022-11-06 10:54 ` [PATCH 2/7] [gdb/testsuite] fix test gdb.base/print-file-var.exp for remote execution Tom de Vries
2022-11-07 13:32 ` Andrew Burgess
2022-11-07 13:49 ` Ivan Tetyushkin
2022-11-07 16:44 ` Tom de Vries
2022-11-15 14:39 ` Tom de Vries
2022-11-07 16:18 ` Tom de Vries
2022-11-07 13:55 ` Simon Marchi
2022-11-07 16:15 ` Tom de Vries
2022-10-25 16:29 ` [PATCH 3/7] [gdb/testsuite] fix test gdb.base/jit-reader-exec.exp " Ivan Tetyushkin
2022-10-25 16:29 ` [PATCH 4/7] [gdb/testsuite] fix test gdb.base/solib-vanish.exp " Ivan Tetyushkin
2022-10-25 16:29 ` [PATCH 5/7] [gdb/testsuite] fix test gdb.base/infcall-exec.exp " Ivan Tetyushkin
2022-10-25 16:29 ` [PATCH 6/7] [gdb/testsuite] fix test gdb.base/info-shared.exp " Ivan Tetyushkin
2022-10-25 16:29 ` [PATCH 7/7] [gdb/testsuite] fix test gdb.base/jit-elf-so.exp " Ivan Tetyushkin
2022-10-29 9:20 ` [PATCH 0/7] introduce get_runtime_path Andrew Burgess
2022-11-01 9:19 ` Ivan Tetyushkin
2022-11-05 14:39 ` 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=20221025162946.727169-3-ivan.tetyushkin@syntacore.com \
--to=ivan.tetyushkin@syntacore.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).