This is the mail archive of the
mailing list for the GDB project.
Re: GDB honouring RPATH in binaries.
On Feb 20, 2:54pm, Kris Warkentin wrote:
> > On Thu, Feb 20, 2003 at 02:44:52PM -0500, Kris Warkentin wrote:
> > > > Question: when do we need to find shared libraries that we can't use a
> > > > full path + solib-absolute-prefix, where RPATH would be in the least
> > > > useful? RPATH only matters when you have multiple places you could
> > > > find the library and are interested in which one you got; if there is
> > > > mapping between target and host filesystems, it should be
> > > > solib-absolute-prefix only.
> > > >
> > > > We generally get full pathnames of loaded modules from the dynamic
> > > > linker, and use that. Is this a problem for QNX?
> > >
> > > In the remote case I suppose it is. The linker on the remote will have
> > > loaded /lib/libc.so.2 or some such but on the host, that will be
> > > $QNX_TARGET/$CPU/lib/libc.so.2. Hence solib-absolute-prefix being set
> > > $QNX_TARGET/$CPU. I'm just looking for better ways to get this all to
> > > together with a minimum of fuss for the end user.
> > I guess I don't see the problem. If we have solib-absolute-prefix set,
> > and we retrieve the string "/lib/libc.so.2" from the remote target...
> You're preaching to the choir. ;-) I'm just trying to form an intelligent
> argument for those in my company who want to use RPATH. In solib_open(), we
> search the inferior's LD_LIBRARY_PATH and PATH as a fallback so I wonder if
> there would be any harm in at least looking at the RPATH? Perhaps if we
> just appended it to solib-search-path or one of the others? I dunno.
> That's why I'm asking.
For remote targets, you must have solib-absolute-prefix set. Searching
host libraries (whether found via RPATH or some other means) is almost