When I look at the dynamically loaded libraries, using the ldd utility, I see a shared object linux-gate.so.1. What is linux-gate.so.1?
When you use the ldd utility on a reasonably recent Linux system you’ll frequently see a reference to an ethereal entity known as linux-gate.so.1: ldd /bin/sh linux-gate.so.1 => (0xffffe000) libdl.so.2 => /lib/libdl.so.2 (0xb7fb2000) libc.so.6 => /lib/libc.so.6 (0xb7e7c000) /lib/ld-linux.so.2 (0xb7fba000) What’s so strange about that? It’s just a dynamically loaded library, right? Sort of, for sufficiently generous definitions of dynamically loaded library. The lack of file name in the output indicates that ldd was unable to locate a file by that name. Indeed, any attempt to find the corresponding file, whether manually or by software designed to automatically load and analyze such libraries, will be unsuccessful. From time to time this is a cause of befuddlement and frustration for users as they go searching for a non-existent system file. You can confidently tell users on this futile quest that there’s not supposed to be a linux-gate.so.1 file present anywhere on the file system; it’
Related Questions
- Why do I get the error message "ERROR while loading shared libraries: libg2c.so.0: cannot open shared object file: No such file or directory" when I try to start Gridgen on my OpenSuse machine?
- When I look at the dynamically loaded libraries, using the ldd utility, I see a shared object linux-gate.so.1. What is linux-gate.so.1?
- Are the shared dynamically linkable libraries portable?
