From: Hui Zhu <hui_zhu@mentor.com>
To: gdb-patches ml <gdb-patches@sourceware.org>
Subject: [PATCH] testsuite: let GDB add a dir to autoload safe-path
Date: Wed, 26 Jun 2013 11:28:00 -0000 [thread overview]
Message-ID: <51CACF09.2040804@mentor.com> (raw)
Hi,
When I use our test environment with GDB test threads, I got some fails because my libthread_db is not in $sdir but in $pdir. But GDB will check saft-path before load libthread_db in $pdir.
So I make a patch to update runto to let it add a dir to safe-path if board file set safe_path. Then for some special test environment, they can add a dir to auto load safe-path if they need.
Please help me review it.
Thanks,
Hui
2013-06-27 Hui Zhu <hui@codesourcery.com>
* lib/gdb.exp(runto): Call add-auto-load-safe-path.
--- a/gdb/testsuite/lib/gdb.exp
+++ b/gdb/testsuite/lib/gdb.exp
@@ -469,6 +469,10 @@ proc runto { function args } {
return 0
}
+ if { [target_info exists safe_path] } {
+ gdb_test "add-auto-load-safe-path [target_info safe_path]"
+ }
+
gdb_run_cmd
# the "at foo.c:36" output we get with -g.
next reply other threads:[~2013-06-26 11:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-26 11:28 Hui Zhu [this message]
2013-06-26 11:53 ` Pedro Alves
2013-06-27 7:28 ` Hui Zhu
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=51CACF09.2040804@mentor.com \
--to=hui_zhu@mentor.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