On Saturday 27 November 2004 11:46, Aliberti Emanuele wrote:
KJK::Hyperion wrote:
I doubt we'll need this. I'll try to add support for querying the interpreter name, but I don't think we really need this for Win32. POSIX maybe (hence a way to query an ELF image section for the interpreter name), but for Win32 I think we're stretching it enough at supporting ELF at all. Then again I don't really know what runtime linkers are for
Hi, is the ELF "interpreter name" what in PE images is the subsystem field?
I don't know the "subsystem field", but I doubt it. The interpreter tells what the kernel should use to "interpret" the image. When an ELF file is loaded it is mapped into memory, then the kernel looks if there is an interpreter (a filename like /lib/ld-linux.so.2) and if there is one it also maps the interpreter file into memory and starts execution at the interpreter's entry point instead of the executable image to be loaded. The interpreter (rtld - runtime link editor) relocates itself and the executable image, sets up other stuff and transfers execution to the executable image's entry point. On windows (for PE files) ntdll is doing that.