Dear Maintainer,

I'm a little puzzled here:

Based on this help:

,----[ LD_DEBUG=help /bin/true ]
| Valid options for the LD_DEBUG environment variable are:
|
|   libs        display library search paths
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|   reloc       display relocation processing
|   files       display progress for input file
|   symbols     display symbol table processing
|   bindings    display information about symbol binding
|   versions    display version dependencies
|   all         all previous options combined
|   statistics  display relocation statistics
|   unused      determined unused DSOs
|   help        display this help message and exit
|
| To direct the debugging output into a file instead of standard output
| a filename can be specified using the LD_DEBUG_OUTPUT environment variable.
`----

I expected this to list the entire library search path:

,----[ LD_DEBUG=libs /bin/true ]
|       3652:	find library=libc.so.6 [0]; searching
|       3652:	 search cache=/etc/ld.so.cache
|       3652:	  trying file=/lib/i386-linux-gnu/i686/cmov/libc.so.6
|       3652:
|       3652:
|       3652:	calling init: /lib/i386-linux-gnu/i686/cmov/libc.so.6
|       3652:
|       3652:
|       3652:	initialize program: /bin/true
|       3652:
|       3652:
|       3652:	transferring control: /bin/true
|       3652:
|       3652:
|       3652:	calling fini: /bin/true [0]
|       3652:
`----

but, as you can see, it didn't.  Is this just an unclear help message,
or is it actually an implementation bug?

Samuel Bronson wrote:
[...]
[...]

The former, I think.  Since it was introduced, LD_DEBUG=libs has only
printed information about how the location of libraries to be loaded
was determined, and when there is no RUNPATH, RPATH, or
LD_LIBRARY_PATH and the library's location is cached, that doesn't
involve printing any search paths.

Any ideas for wording it better?

Hope that helps,
Jonathan