Question

What is the search order for symbol lookup when resolving dynamic relocations?

When resolving symbols for a shared library does the loader first search in the ‘main executable’ (to let the main executable override definitions…) or what?

Answer 1

Per my understanding, each executable object has its own “lookup scope”:

• The main executable is usually the first object in the “global” lookup scope. This means that symbols defined in the main executable would override those in dependent shared libraries. Shared objects that are added using the LD_PRELOAD facility are added to the global lookup scope, right after the main executable.
• However, if the shared object being loaded uses the DF_SYMBOLIC flag, then symbol references that originate within that object will look for definitions within the object before searching in the global lookup scope.
• Shared objects opened using dlopen() may have their own dependencies. If the RTLD_GLOBAL flag was not set during the call to dlopen(), these dependencies are added to the lookup scope for that object, but do not affect the global lookup scope. If the RTLD_GLOBAL flag was passed to dlopen(), then the shared object (and its dependencies) will be added to the “global” lookup scope, changing the behavior of subsequent symbol lookups.

Ulrich Drepper’s guide “How to Write Shared Libraries” is recommended reading on this topic.