[klibc] testers sought for script to interpret ELF/klibc executables

H. Peter Anvin hpa at zytor.com
Sun Mar 6 12:50:05 PST 2005

Erik van Konijnenburg wrote:
> Oh, it finds the interp for executables regardless of which library is
> used.  Just not the shared libraries, but for glibc ldd handles that
> and klibc does not support shared libraries (correct me if I'm wrong;
> I could not find a loader in the sources).

Right.  I meant, it would be easy for it to handle non-native binaries 
as well.

>>>The tricky part is that perl unpacking of 64-bit integers has
>>>limitations: only available on 64-bit machines, only if configured in.
>>>If it turns out this causes problems in practise, I'll have to rework
>>>this to unpack 64-bit ints as two longs; something I'd rather avoid.
>>Sounds like a good reason to write it in C instead.
> You're probably right.  See also Debian bug #298311, "new ldd breaks
> initrd-tools on amd64".  This tool would need to:
> - be based on bfd,
> - find interp, the dynamic loader
> - find the NEEDED records from the .dynamic segment
> - apply LD_LIBRARY_PATH to such records

No need to base it on bfd.  For just extracting the interpreter, there 
is pretty much a pointer in the ELF header.


More information about the klibc mailing list