Loaderpath

Loaderpath is the search path used by a program's runtime loader to locate shared libraries, plugins, and modules required at run time. It represents the directories that the loader will consult in order when resolving dependencies before an application runs, and it can influence which library versions are loaded.

The loaderpath is typically formed from a combination of default system directories, application-specified paths, and environment settings. On Unix-like systems, common elements include standard library directories (such as /lib and /usr/lib), directories specified in environment variables like LD_LIBRARY_PATH, and paths embedded in executables as RPATH or RUNPATH. Applications may also contribute additional loader paths through configuration files or command-line options. On Windows, the loader path is influenced by the directory containing the executable, system directories, and directories listed in the PATH environment variable, with some platform features providing additional probing rules.

Loaderpath is important for dependency resolution, version management, and isolation of an application's runtime environment. It enables loading of multiple library versions or optional plugins, but misconfigurations can lead to conflicts, missing dependencies, or security risks such as library hijacking. Proper management often involves restricting or carefully controlling which directories are searched, using per-application vendor bundles, and avoiding overly broad global search paths.

Related concepts include dynamic linker behavior, RPATH/RUNPATH and LD_LIBRARY_PATH on Unix-like systems, and similar probing mechanisms in other runtimes. Understanding loaderpath helps diagnose startup failures, dependency issues, and performance implications related to dynamic loading.