HP-UX Reference (11i v3 07/02) - 3 Library Functions N-Z (vol 7)

shl_load_ia(3X)

Integrity Systems Only

shl_load_ia(3X)

[ENOMEM] There is insufﬁcient room in the address space to load the library.

[ENOENT] The speciﬁed path does not exist, or the speciﬁed handle is invalid.

[ETXTBSY] The speciﬁed shared library is currently in use and cannot be unloaded.

[EACCES] Read or execute permission is denied for the speciﬁed library.

WARNINGS

shl_unload() detaches the library from the process and frees the memory allocated for it, but does not

break existing symbolic linkages into the library. In this respect, an unloaded shared library is much like a

block of memory deallocated via free() (see malloc(3C)).

Some implementations may not, by default, export all symbols deﬁned by a program (instead exporting only

those symbols that are imported by a shared library seen at link time). Therefore the

-E option to ld(1)

should be used when using these routines if the loaded libraries are to refer to program symbols.

All symbol information returned by

shl_getsymbols()

, including the name ﬁeld, become invalid once

the associated library is unloaded by

shl_unload()

. This is also true if a library is unloaded by a call to

dlclose().

Use caution when building shared libraries with external library dependencies. Any library that contains

Thread Local Storage (TLS) and uses static TLS model should not be used as a dependency. See "Thread

Local Storage" in dld.so(5) for more information. If a dependent library contains TLS, was built with static

TLS model and it is not loaded during program startup (that is, not linked against the executable), the

dynamic loader fails to perform the operation. You can use +tls=dynamic compiler option to re-compile

the library to avoid errors.

When a routine or ﬂag is used which may not be supported in the future, the dynamic loader can display a

warning message. See the WARNINGS section in dld.sl(5) for further details.

Future HP-UX environments may not support these routines and ﬂags or may only support a subset of

them. Instead, they will use the SVR4 dynamic loading API. Users are encouraged to migrate to the

dl*

family of dynamic linking routines. See the dlclose(3C), dlerror(3C), dlget(3C), dlgetname(3C),

dlmodinfo(3C), dlopen(3C), and dlsym(3C) man pages for more information.

AUTHOR

shl_load(3X) and related functions were developed by HP.