From: "Kris Warkentin" <kewarken@qnx.com>
To: "Gdb@Sources.Redhat.Com" <gdb@sources.redhat.com>
Subject: Why does solib_open do what it does?
Date: Tue, 17 Jun 2003 19:01:00 -0000 [thread overview]
Message-ID: <09c201c33502$da555ce0$0202040a@catdog> (raw)
I'm looking at solib.c:solib_open() and as I go down the list:
Search order:
1 * If path is absolute, look in SOLIB_ABSOLUTE_PREFIX.
2 * If path is absolute or relative, look for it literally (unmodified).
3 * Look in SOLIB_SEARCH_PATH.
4 * If available, use target defined search function.
5 * Look in inferior's $PATH.
6 * Look in inferior's $LD_LIBRARY_PATH.
I'm puzzled. Why are we testing for the existence of solib_search_path
before checking 5 and 6?
cheers,
Kris
next reply other threads:[~2003-06-17 19:01 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 19:01 Kris Warkentin [this message]
2003-06-17 19:13 ` Daniel Jacobowitz
2003-06-17 19:14 ` Kris Warkentin
2003-06-17 19:37 ` Elena Zannoni
2003-06-17 19:47 ` Kris Warkentin
2003-06-17 20:01 ` Kevin Buettner
2003-06-17 20:15 ` Kris Warkentin
2003-06-17 20:24 ` Kevin Buettner
2003-06-18 0:14 ` Michael Snyder
2003-06-18 1:43 ` Kris Warkentin
2003-06-18 5:33 ` Kevin Buettner
2003-06-18 12:11 ` Kris Warkentin
2003-06-18 15:07 ` Kris Warkentin
2003-06-18 18:52 ` Michael Snyder
2003-06-18 19:09 ` Kris Warkentin
2003-06-18 19:20 ` Andrew Cagney
2003-06-18 20:10 ` Michael Snyder
2003-06-18 20:17 ` Kris Warkentin
2003-06-18 19:14 ` Daniel Jacobowitz
2003-06-18 18:45 ` Michael Snyder
2003-06-18 18:41 ` Michael Snyder
2003-06-18 19:16 ` Daniel Jacobowitz
2003-06-18 20:11 ` Michael Snyder
2003-06-18 20:19 ` Kris Warkentin
2003-06-18 20:27 ` Daniel Jacobowitz
2003-06-18 20:51 ` Michael Snyder
2003-06-19 12:24 ` Kris Warkentin
2003-06-19 23:33 ` Kevin Buettner
2003-06-20 0:02 ` Kevin Buettner
2003-06-20 12:28 ` Kris Warkentin
2003-06-20 12:43 ` Kevin Buettner
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='09c201c33502$da555ce0$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=gdb@sources.redhat.com \
/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