Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

dlclose(3c) [sunos man page]

dlclose(3C)						   Standard C Library Functions 					       dlclose(3C)

NAME
dlclose - close a shared object SYNOPSIS
#include <dlfcn.h> int dlclose(void *handle); DESCRIPTION
The dlclose() function decrements the reference count of the supplied handle. This handle represents an executable object file and its dependencies, acquired from a previous call to dlopen(). A handle that is no longer referenced is processed in an attempt to unload any objects that are associated with the handle from the current process. An unreferenced handle is no longer available to dlsym(). Any finalization code within an object is executed prior to that object being unloaded. Any routines registered by an object using atexit(3C) are called prior to that object being unloaded. See NOTES. RETURN VALUES
If the handle was successfully unreferenced, dlclose() returns 0. If the handle is invalid, or an error occurred as a result of unloading an object, dlclose() returns a non-zero value. Additional diagnostic information is available through dlerror(). USAGE
The dlclose() function is one of a family of functions that give the user direct access to the dynamic linking facilities. These facilities are available to dynamically-linked processes only. See the Linker and Libraries Guide. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Interface Stability |Standard | +-----------------------------+-----------------------------+ |MT-Level |MT-Safe | +-----------------------------+-----------------------------+ SEE ALSO
ld(1), ld.so.1(1), atexit(3C), dladdr(3C), dldump(3C), dlerror(3C), dlopen(3C), dlsym(3C), attributes(5), standards(5) Linker and Libraries Guide NOTES
A successful invocation of dlclose() does not guarantee that the objects associated with the handle are removed from the address space of the current process. Objects can be referenced by multiple handles, or by other objects. An object is not removed from the address space of the current process until all references to that object are removed. Once an object has been closed by dlclose(), referencing symbols contained in that object can cause undefined behavior. As part of unloading an object, finalization code within the object is called before the dlclose() returns. This finalization is user code, and as such, can produce errors that can not be caught by dlclose(). For example, an object loaded using RTLD_LAZY that attempts to call a function that can not be located, results in process termination. Erroneous programming practices within the finalization code can also result in process termination. The runtime linkers debugging facility can offer help identifying these types of error. See the LD_DEBUG environment variable of ld.so.1(1). SunOS 5.10 1 March 2004 dlclose(3C)

Check Out this Related Man Page

dlclose(3C)															       dlclose(3C)

NAME
dlclose() - close a shared library SYNOPSIS
[flag ... ] file ... [library]... Multithread Usage This routine is thread-safe. NOTE: The dynamic loader serializes the loading and unloading of shared libraries in multithreaded applications using a recursive pthread mutex lock. See the for more information. DESCRIPTION
is one of a family of routines that give the user direct access to the dynamic linking facilities (using the option on the compiler or com- mand line). disassociates a shared object previously opened by from the current process. Once an object has been closed using its symbols are no longer available to All objects loaded automatically as a result of invoking on the referenced object (see dlopen(3C)) are also closed. handle is the value returned by a previous invocation of RETURN VALUE
If the referenced object was successfully closed, returns If the object could not be closed, or if handle does not refer to an open object, returns a non-0 value. More detailed diagnostic information is available through ERRORS
If fails, a subsequent call to returns one of the following values. Cannot apply relocation in library. Cannot close library due to remaining dependencies. Invalid handle. Out of memory. failed on entry to or exit from failed on exit from failed on entry to Unknown handle. WARNINGS
A successful invocation of does not guarantee that the objects associated with handle have actually been removed from the address space of the process. Objects loaded by one invocation of may also be loaded by another invocation of The same object may also be opened multiple times. An object is not removed from the address space until all references to that object through an explicit invocation have been closed and all other objects implicitly referencing that object have also been closed. Once an object has been closed by referencing symbols contained in that object can cause undefined behavior. SEE ALSO
dlerrno(3C), dlerror(3C), dlopen(3C), dlsym(3C). Texts and Tutorials (See the option) (See manuals(5) for ordering information) dlclose(3C)
Man Page