This is the mail archive of the libc-alpha@sourceware.org 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


On Fri, Jun 24, 2016 at 7:31 PM, Pedro Alves <palves@redhat.com> wrote:
> How about:
>
> - add whatever lines those are to a gdb script that lives along
>   side the tests.
>
> - have the harness start gdb with:
>
>    gdb -nx -ix /path/to/that/script
>
> No need to manually tweak ~/.gdbinit that way.

Sounds good! I'll see about adding that when I send the install patch
though, as I'd like to wrap this one up first.

On Sat, Jun 25, 2016 at 1:44 AM, Siddhesh Poyarekar
<siddhesh@sourceware.org> wrote:
> (To elaborate on my last response, since I realized I did not explain
> the mechanics of how this works)

Thanks for the thorough explanation.

> Your default dynamic linker is being set as the built one instead of
> the system, perhaps because of the way your source is configured.

Funny, I actually thought it was supposed to do that :)

> 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.

Maybe the built ld.so somehow knows where to find the built libraries,
as if my custom install dir was some sort of sysroot?

> 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 checked rtldir and slibdir, and both are empty. So are
LD_LIBRARY_PATH and LD_RUN_PATH. I never used anything weird for my
configure, just --prefix=/home/martin/glibc/install as always.

It would be great if you could tell me what flags are being passed to
gcc when you compile the tests. Your gdb version, as well as the
output of info share, might also give us a clue.


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