For Solaris 8 1/01 release, Linker and Libraries Guide has
been updated with the following information.
|
-
The symbolic information available from dladdr(3DL) has been enhanced with the introduction of dladdr1().
-
The $ORIGIN of a dynamic object can be
obtained from dlinfo(3DL).
-
The maintenance of runtime configuration files, created with crle(1), has been simplified with the display of the command-line
options that were used to create the configuration file. Also available is
an update capability (see the -u option).
-
The runtime linker and its debugger interface have been extended
to detect procedure-linkage-table entry resolution. This update is identified
by a new version number. See the section “Agent Manipulation.”
This update extends the rd_plt_info_t structure. See the section “Procedure
Linkage Table Skipping.”
-
An applications stack can be defined non-executable by using
the new mapfile segment descriptor STACK. See the section “Segment
Declarations.”
|
For the Solaris 8 10/00 release, Linker and Libraries Guide has
been updated with the following information.
|
-
The environment variable LD_BREADTH is ignored
by the runtime linker. See the section, “Initialization and Termination
Routines.”
-
The runtime linker and its debugger interface have been extended
for better runtime and core file analysis. This update is identified by a
new version number. See the section “Agent Manipulation.” This
update expands the rl_flags, rl_bend, and rl_dynamic fields of the rd_loadobj_t
structure. See the section “Scanning Loadable Objects.”
-
The validation of displacement-relocated data in regard to
its use, or possible use, with copy relocations is now provided. See the section “Displacement
Relocations.”
-
64-bit filters can be built solely from a mapfile by using
the link-editors -64 option. See the section “Generating
a Standard Filter.”
-
Some explanatory notes are provided on why $ORIGIN dynamic string token expansion is restricted within secure applications.
See the section “Security.”
-
The search paths that are used to locate the dependencies
of dynamic objects can be inspected by using dlinfo(3DL).
-
dlsym(3DL) and dlinfo(3DL)
look-up semantics have been expanded with a new handle, RTLD_SELF.
-
The runtime symbol look-up mechanism that is used to relocate
dynamic objects can be significantly reduced by establishing direct binding
information within each dynamic object. See the sections “External Bindings”
or “Direct Binding.”
|