This is the mail archive of the mailing list for the glibc project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH v8] Add pretty printers for the NPTL lock types

(To elaborate on my last response, since I realized I did not explain
the mechanics of how this works)

On Fri, Jun 24, 2016 at 05:46:23PM -0300, Martin Galvan wrote:
> I added an endless loop to the test code, so that I could examine its
> proc mappings without running it through gdb, and I'm still seeing the
> built libraries. And yeah, you're right in that it's being compiled
> using rpath-link:

Your default dynamic linker is being set as the built one instead of
the system, perhaps because of the way your source is configured.
That alone does not however determine why your program picks up the
built libraries because you've only specified rpath-link and not rpath
and hence the binary itself does not have the paths to search from.

So the question is how the binary ends up picking the built libraries
and the answer might be in why your build system picks up the built
dynamic linker.  Check out your rtldir and slibdir in the generated
config.make and that might tell you why.  I think there is some system
configuration on your computer that ends up in picking the built
libraries, either LD_LIBRARY_PATH set somewhere or something you
specified in configure, although the latter seems unlikely.

I'll run tests tonight but you might want to try your entire exercise
on a different computer and with a very basic configure command:

    ../configure --prefix=/usr


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]