[uClibc] ld.so loading "false" libs

[Peter S. Mazinger]

On Tue, 28 Sep 2004, Erik Andersen wrote:

> On Sat Sep 25, 2004 at 03:55:02PM +0200, Peter S. Mazinger wrote:
> > Could this be related to the fact that running ldd it shows all the time 
> > (0x00000000) after the used lib (as opposed to glibc's ldd, where there 
> > are different values,
> 
> uClibc's ldd first checks if the target binary is the correct
> architecture, binary type, etc, and then attempts to execute
> the binary with a special env variable set so that ldso will
> instead print a list of the NEEDED shared libs and the memory
> locations where they are loaded.
> 
> If the above fails, unlike glibc's ldd, uClibc's ldd will then
> grovel about in the binary's ELF header, print a list of the
> NEEDED shared libs, and attempt to provide a best-guess of where
> those shared libraries might be found.  In this fallback,
> best-guess case, a load value of 0x00000000 is displayed.

Thanks catching up, it is solved already, only ET_EXEC binaries showed the 
address, adding also ET_DYN (mine were built as PIE, also applies to libs)
corrects the problem.

Peter

-- 
Peter S. Mazinger <ps dot m at gmx dot net>           ID: 0xA5F059F2
Key fingerprint = 92A4 31E1 56BC 3D5A 2D08  BB6E C389 975E A5F0 59F2


____________________________________________________________________
Miert fizetsz az internetert? Korlatlan, ingyenes internet hozzaferes a FreeStarttol.
Probald ki most! http://www.freestart.hu