1 .\" Copyright 1995 Yggdrasil Computing, Incorporated.
2 .\" written by Adam J. Richter (adam@yggdrasil.com),
3 .\" with typesetting help from Daniel Quinlan (quinlan@yggdrasil.com).
4 .\" and Copyright 2003, 2015 Michael Kerrisk (mtk.manpages@gmail.com).
6 .\" %%%LICENSE_START(GPLv2+_DOC_FULL)
7 .\" This is free documentation; you can redistribute it and/or
8 .\" modify it under the terms of the GNU General Public License as
9 .\" published by the Free Software Foundation; either version 2 of
10 .\" the License, or (at your option) any later version.
12 .\" The GNU General Public License's references to "object code"
13 .\" and "executables" are to be interpreted as the output of any
14 .\" document formatting or typesetting system, including
15 .\" intermediate and printed output.
17 .\" This manual is distributed in the hope that it will be useful,
18 .\" but WITHOUT ANY WARRANTY; without even the implied warranty of
19 .\" MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
20 .\" GNU General Public License for more details.
22 .\" You should have received a copy of the GNU General Public
23 .\" License along with this manual; if not, see
24 .\" <http://www.gnu.org/licenses/>.
27 .\" Modified by David A. Wheeler <dwheeler@dwheeler.com> 2000-11-28.
28 .\" Applied patch by Terran Melconian, aeb, 2001-12-14.
29 .\" Modified by Hacksaw <hacksaw@hacksaw.org> 2003-03-13.
30 .\" Modified by Matt Domsch, 2003-04-09: _init and _fini obsolete
31 .\" Modified by Michael Kerrisk <mtk.manpages@gmail.com> 2003-05-16.
32 .\" Modified by Walter Harms: dladdr, dlvsym
33 .\" Modified by Petr Baudis <pasky@suse.cz>, 2008-12-04: dladdr caveat
35 .TH DLOPEN 3 2015-03-29 "Linux" "Linux Programmer's Manual"
37 dlclose, dlopen, dlmopen \-
38 open and close a shared object
42 .BI "void *dlopen(const char *" filename ", int " flags );
44 .BI "int dlclose(void *" handle );
46 .B #define _GNU_SOURCE
50 .BI "void *dlmopen (Lmid_t " lmid ", const char *" filename ", int " flags );
52 Link with \fI\-ldl\fP.
57 loads the dynamic shared object (shared library)
58 file named by the null-terminated
61 and returns an opaque "handle" for the loaded object.
64 is NULL, then the returned handle is for the main program.
67 contains a slash ("/"), then it is interpreted as a (relative
68 or absolute) pathname.
69 Otherwise, the dynamic linker searches for the object as follows
74 (ELF only) If the executable file for the calling program
75 contains a DT_RPATH tag, and does not contain a DT_RUNPATH tag,
76 then the directories listed in the DT_RPATH tag are searched.
78 If, at the time that the program was started, the environment variable
80 was defined to contain a colon-separated list of directories,
81 then these are searched.
82 (As a security measure, this variable is ignored for set-user-ID and
83 set-group-ID programs.)
85 (ELF only) If the executable file for the calling program
86 contains a DT_RUNPATH tag, then the directories listed in that tag
93 is checked to see whether it contains an entry for
100 are searched (in that order).
102 If the object specified by
104 has dependencies on other shared objects,
105 then these are also automatically loaded by the dynamic linker
106 using the same rules.
107 (This process may occur recursively,
108 if those objects in turn have dependencies, and so on.)
110 One of the following two values must be included in
114 Perform lazy binding.
115 Only resolve symbols as the code that references them is executed.
116 If the symbol is never referenced, then it is never resolved.
117 (Lazy binding is performed only for function references;
118 references to variables are always immediately bound when
119 the shared object is loaded.)
122 If this value is specified, or the environment variable
124 is set to a nonempty string,
125 all undefined symbols in the shared object are resolved before
128 If this cannot be done, an error is returned.
130 Zero or more of the following values may also be ORed in
134 The symbols defined by this shared object will be
135 made available for symbol resolution of subsequently loaded shared objects.
138 This is the converse of
140 and the default if neither flag is specified.
141 Symbols defined in this shared object are not made available to resolve
142 references in subsequently loaded shared objects.
144 .BR RTLD_NODELETE " (since glibc 2.2)"
145 Do not unload the shared object during
147 Consequently, the object's static variables are not reinitialized
148 if the object is reloaded with
151 This flag is not specified in POSIX.1-2001.
152 .\" (But it is present on Solaris.)
154 .BR RTLD_NOLOAD " (since glibc 2.2)"
155 Don't load the shared object.
156 This can be used to test if the object is already resident
158 returns NULL if it is not, or the object's handle if it is resident).
159 This flag can also be used to promote the flags on a shared object
160 that is already loaded.
161 For example, a shared object that was previously loaded with
164 .BR RTLD_NOLOAD\ |\ RTLD_GLOBAL .
165 This flag is not specified in POSIX.1-2001.
166 .\" (But it is present on Solaris.)
169 .BR RTLD_DEEPBIND " (since glibc 2.3.4)"
170 .\" Inimitably described by UD in
171 .\" http://sources.redhat.com/ml/libc-hacker/2004-09/msg00083.html.
172 Place the lookup scope of the symbols in this
173 shared object ahead of the global scope.
174 This means that a self-contained object will use
175 its own symbols in preference to global symbols with the same name
176 contained in objects that have already been loaded.
177 This flag is not specified in POSIX.1-2001.
181 is NULL, then the returned handle is for the main program.
184 this handle causes a search for a symbol in the main program,
185 followed by all shared objects loaded at program startup,
186 and then all shared objects loaded by
191 External references in the shared object are resolved using the
192 shared objects in that object's dependency list and any other
193 objects previously opened with the
196 If the executable was linked with the flag "\-rdynamic"
197 (or, synonymously, "\-\-export\-dynamic"),
198 then the global symbols in the executable will also be used
199 to resolve references in a dynamically loaded shared object.
201 If the same shared object is loaded again with
203 the same object handle is returned.
204 The dynamic linker maintains reference
205 counts for object handles, so a dynamically loaded shared object is not
208 has been called on it as many times as
211 Any initialization returns (see below) are called just once.
212 However, a subsequent
214 call that loads the same shared object with
216 may force symbol resolution for a shared object earlier loaded with
221 fails for any reason, it returns NULL.
224 This function performs the same task as
229 arguments, as well as the return value, are the same,
230 except for the differences noted below.
234 function differs from
236 primarily in that it accepts an additional argument,
238 that specifies the link-map list (also referred to as a
240 in which the shared object should be loaded.
243 adds the dynamically loaded shared object to the same namespace as
244 the shared object from which the
249 type is an opaque handle that refers to a namespace.
253 argument is either the ID of an existing namespace
254 .\" FIXME: Is using dlinfo() RTLD_DI_LMID the right technique?
255 (which can be obtained using the
258 request) or one of the following special values:
261 Load the shared object in the initial namespace
262 (i.e., the application's namespace).
265 Create a new namespace and load the shared object in that namespace.
266 The object must have been correctly linked
267 to reference all of the other shared objects that it requires,
268 since the new namespace is initially empty.
272 is NULL, then the only permitted value for
279 decrements the reference count on the
280 dynamically loaded shared object referred to by
282 If the reference count drops to zero,
283 then the object is unloaded.
284 All shared objects that were automatically loaded when
286 was invoked on the object referred to by
288 are recursively closed in the same manner.
294 return a non-NULL handle for the loaded library.
296 (file could not be found, was not readable, had the wrong format,
297 or caused errors during loading),
298 these functions return NULL.
302 returns 0; on error, it returns a nonzero value.
304 Errors from these functions can be diagnosed using
310 are present in glibc 2.0 and later.
312 first appeared in glibc 2.3.4.
314 POSIX.1-2001 describes
320 function is a GNU extension.
323 .\" The string returned by
325 .\" should not be modified.
326 .\" Some systems give the prototype as
329 .\" .B "const char *dlerror(void);"
334 can be used to register an exit handler that is automatically
335 called when a shared object is unloaded.
337 .SS dlmopen() and namespaces
338 A link-map list defines an isolated namespace for the
339 resolution of symbols by the dynamic linker.
341 dependent shared objects are implicitly loaded according to the usual rules,
342 and symbol references are likewise resolved according to the usual rules,
343 but such resolution is confined to the definitions provided by the
344 objects that have been (explicitly and implicitly) loaded into the namespace.
348 function permits object-load isolation\(emthe ability
349 to load a shared object in a new namespace without
350 exposing the rest of the application to the symbols
351 made available by the new object.
352 Note that the use of the
354 flag is not sufficient for this purpose,
355 since it prevents a shared object's symbols from being available to
359 we may want to make the symbols provided by a dynamically
360 loaded shared object available to (a subset of) other shared objects
361 without exposing those symbols to the entire application.
362 This can be achieved by using a separate namespace and the
368 are plugins where the author of the plugin-loading framework
369 can't trust the plugin authors and does not wish
370 any undefined symbols from the plugin framework to be resolved to plugin
372 Another use is to load the same object more than once.
375 this would require the creation of distinct copies of the shared object file.
378 this can be achieved by loading the same shared object file into
379 different namespaces.
381 The glibc implementation supports a maximum of
385 .SS Initialization and finalization functions
386 Shared objects may export functions using the
387 .B __attribute__((constructor))
389 .B __attribute__((destructor))
391 Constructor functions are executed before
393 returns, and destructor functions are executed before
396 A shared object may export multiple constructors and destructors,
397 and priorities can be associated with each function
398 to determine the order in which they are executed.
401 info pages (under "Function attributes")
402 .\" info gcc "C Extensions" "Function attributes"
403 for further information.
405 An older method of (partially) achieving the same result is via the use of
406 two special symbols recognized by the linker:
410 If a dynamically loaded shared object exports a routine named
412 then that code is executed after loading a shared object, before
415 If the shared object exports a routine named
417 then that routine is called just before the object is unloaded.
418 In this case, one must avoid linking against the system startup files,
419 which contain default versions of these files;
420 this can be done by using the
429 is now deprecated in favor of the aforementioned
430 constructors and destructors,
431 which among other advantages,
432 permit multiple initialization and finalization functions to be defined.
434 .\" Using these routines, or the gcc
435 .\" .B \-nostartfiles
438 .\" options, is not recommended.
439 .\" Their use may result in undesired behavior,
440 .\" since the constructor/destructor routines will not be executed
441 .\" (unless special measures are taken).
442 .\" .\" void _init(void) __attribute__((constructor));
443 .\" .\" void _fini(void) __attribute__((destructor));
446 These functions are part of the dlopen API, derived from SunOS.
448 Load the math library, and print the cosine of 2.0:
456 main(int argc, char **argv)
459 double (*cosine)(double);
462 handle = dlopen("libm.so", RTLD_LAZY);
464 fprintf(stderr, "%s\en", dlerror());
468 dlerror(); /* Clear any existing error */
470 cosine = (double (*)(double)) dlsym(handle, "cos");
472 /* According to the ISO C standard, casting between function
473 pointers and 'void *', as done above, produces undefined results.
474 POSIX.1-2003 and POSIX.1-2008 accepted this state of affairs and
475 proposed the following workaround:
477 *(void **) (&cosine) = dlsym(handle, "cos");
479 This (clumsy) cast conforms with the ISO C standard and will
480 avoid any compiler warnings.
482 The 2013 Technical Corrigendum to POSIX.1-2008 (a.k.a.
483 POSIX.1-2013) improved matters by requiring that conforming
484 implementations support casting 'void *' to a function pointer.
485 Nevertheless, some compilers (e.g., gcc with the '-pedantic'
486 option) may complain about the cast used in this program. */
487 .\" http://pubs.opengroup.org/onlinepubs/009695399/functions/dlsym.html#tag_03_112_08
488 .\" http://pubs.opengroup.org/onlinepubs/9699919799/functions/dlsym.html#tag_16_96_07
489 .\" http://austingroupbugs.net/view.php?id=74
493 fprintf(stderr, "%s\en", error);
497 printf("%f\en", (*cosine)(2.0));
503 As at glibc 2.21, specifying the
507 .\" dlerror(): "invalid mode"
509 Furthermore, specifying
513 results in a program crash
515 if the call is made from any object loaded in a
516 namespace other than the initial namespace.
521 .BR dl_iterate_phdr (3),
530 gcc info pages, ld info pages