| Skip Navigation Links | |
| Exit Print View | |
|
Linker and Libraries Guide Oracle Solaris 10 1/13 Information Library |
| Skip Navigation Links | |
| Exit Print View | |
|
|
Linker and Libraries Guide Oracle Solaris 10 1/13 Information Library |
Part I Using the Link-Editor and Runtime Linker
1. Introduction to the Oracle Solaris Link Editors
5. Link-Editor Quick Reference
7. Building Objects to Optimize System Performance
10. Establishing Dependencies with Dynamic String Tokens
Part IV ELF Application Binary Interface
13. Program Loading and Dynamic Linking
A. Linker and Libraries Updates and New Features
Oracle Solaris 10 1/13 Release
Oracle Solaris 10 8/11 Release
The environment variable LD_BREADTH is ignored by the runtime linker. See 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 rd_init() under Agent Manipulation Interfaces. This update extends the rd_loadobj_t structure. See Scanning Loadable Objects.
You can validate displacement relocated data in regard to its use, or possible use, with copy relocations. See Displacement Relocations.
64–bit filters can be built solely from a mapfile by using the link-editor's -64 option. See Generating Standard Filters.
The search paths used to locate the dependencies of dynamic objects can be inspected using dlinfo(3C).
dlsym(3C) and dlinfo(3C) lookup semantics have been expanded with a new handle RTLD_SELF.
The runtime symbol lookup mechanism used to relocate dynamic objects can be significantly reduced by establishing direct binding information within each dynamic object. See Chapter 6, Direct Bindings.
|