From: Kevin Buettner <kevinb@redhat.com>
To: Daniel Jacobowitz <drow@mvista.com>, jorma.laaksonen@hut.fi
Cc: gdb-gnats@sources.redhat.com, gdb@sources.redhat.com
Subject: Re: gdb/633: fully qualified pathnames in solib_map_sections() and remote debugging
Date: Fri, 09 Aug 2002 16:12:00 -0000 [thread overview]
Message-ID: <1020809231206.ZM11775@localhost.localdomain> (raw)
In-Reply-To: Daniel Jacobowitz <drow@mvista.com> "Re: gdb/633: fully qualified pathnames in solib_map_sections() and remote debugging" (Aug 6, 9:20am)
On Aug 6, 9:20am, Daniel Jacobowitz wrote:
> Global variable SOLIB_ABSOLUTE_PREFIX is used as a prefix directory
> to search for shared libraries if they have an absolute path.
>
> Global variable SOLIB_SEARCH_PATH is used as a prefix directory
> (or set of directories, as in LD_LIBRARY_PATH) to search for all
> shared libraries if not found in SOLIB_ABSOLUTE_PREFIX.
>
> Search order:
> * If path is absolute, look in SOLIB_ABSOLUTE_PREFIX.
> * If path is absolute or relative, look for it literally (unmodified).
> * Look in SOLIB_SEARCH_PATH.
> * Look in inferior's $PATH.
> * Look in inferior's $LD_LIBRARY_PATH.
>
>
> I think the search order needs some revision though:
> - A cross debugger should not search $PATH or $LD_LIBRARY_PATH
I agree with this.
> - A cross debugger may, or may not, want to look for the unmodified
> path; I suspect that we only want to look for unmodified relative
> paths, not unmodified absolute ones.
I agree regarding absolute paths.
For relative paths, I'm not convinced that it's all that useful to
look at the unmodified path. (Doing so requires that you have your
cwd set correctly, right?)
> With those changes you would have to explicitly specify the path to
> DSOs in a cross debugger via solib-absolute-prefix and
> solib-search-path,
I think this would be good...
> and GDB would stop picking up the host libpthread.so
> and making gdbserver segfault...
...and this too!
Kevin
next prev parent reply other threads:[~2002-08-09 23:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020806100634.11483.qmail@sources.redhat.com>
2002-08-06 6:20 ` Daniel Jacobowitz
2002-08-09 16:12 ` Kevin Buettner [this message]
2002-08-11 20:25 ` Daniel Jacobowitz
2002-08-12 4:18 ` Jorma Laaksonen
2002-08-12 7:28 ` Andrew Cagney
2002-08-12 7:37 ` Daniel Jacobowitz
2002-08-12 8:07 ` Andrew Cagney
2002-08-12 8:48 ` Kevin Buettner
2002-08-12 8:55 ` Daniel Jacobowitz
2002-08-12 9:20 ` Kevin Buettner
2002-08-12 9:29 ` Daniel Jacobowitz
2002-08-12 9:20 ` Andrew Cagney
2002-08-12 9:31 ` Daniel Jacobowitz
2002-08-12 9:40 ` Kevin Buettner
2002-08-12 9:53 ` GDB functionalities for debugging Elf core dump Lucy Zhang
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=1020809231206.ZM11775@localhost.localdomain \
--to=kevinb@redhat.com \
--cc=drow@mvista.com \
--cc=gdb-gnats@sources.redhat.com \
--cc=gdb@sources.redhat.com \
--cc=jorma.laaksonen@hut.fi \
/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