1 .\" Copyright (c) 1993 Paul Kranenburg
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice, this list of conditions and the following disclaimer.
9 .\" 2. Redistributions in binary form must reproduce the above copyright
10 .\" notice, this list of conditions and the following disclaimer in the
11 .\" documentation and/or other materials provided with the distribution.
12 .\" 3. All advertising materials mentioning features or use of this software
13 .\" must display the following acknowledgement:
14 .\" This product includes software developed by Paul Kranenburg.
15 .\" 3. The name of the author may not be used to endorse or promote products
16 .\" derived from this software without specific prior written permission
18 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
19 .\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
20 .\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
21 .\" IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT,
22 .\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
23 .\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
24 .\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
25 .\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
26 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
27 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
29 .\" $FreeBSD: src/share/man/man5/link.5,v 1.14.2.10 2004/05/17 11:38:55 brueffer Exp $
30 .\" $DragonFly: src/share/man/man5/link.5,v 1.6 2006/10/14 23:59:59 swildner Exp $
37 .Nd dynamic loader and link editor interface
45 declares several structures that are present in dynamically linked
46 programs and libraries.
47 The structures define the interface between several components of the
48 link-editor and loader mechanism.
49 The layout of a number of these
50 structures within the binaries resembles the a.out format in many places
51 as it serves such similar functions as symbol definitions (including the
52 accompanying string table) and relocation records needed to resolve
53 references to external entities.
54 It also records a number of data structures
55 unique to the dynamic loading and linking process.
56 These include references
57 to other objects that are required to complete the link-editing process and
58 indirection tables to facilitate
59 .Em Position Independent Code
60 (PIC for short) to improve sharing of code pages among different processes.
61 The collection of data structures described here will be referred to as the
62 .Em Run-time Relocation Section (RRS)
63 and is embedded in the standard text and data segments of the dynamically
64 linked program or shared object image as the existing
66 format offers no room for it elsewhere.
68 Several utilities cooperate to ensure that the task of getting a program
69 ready to run can complete successfully in a way that optimizes the use
71 The compiler emits PIC code from which shared libraries
74 The compiler also includes size information of any initialized data items
75 through the .size assembler directive.
76 PIC code differs from conventional code
77 in that it accesses data variables through an indirection table, the
78 Global Offset Table, by convention accessible by the reserved name
79 .Dv _GLOBAL_OFFSET_TABLE_ .
80 The exact mechanism used for this is machine dependent, usually a machine
81 register is reserved for the purpose.
82 The rational behind this construct
83 is to generate code that is independent of the actual load address.
85 the values contained in the Global Offset Table may need updating at run-time
86 depending on the load addresses of the various shared objects in the address
89 Likewise, procedure calls to globally defined functions are redirected through
90 the Procedure Linkage Table (PLT) residing in the data segment of the core
92 Again, this is done to avoid run-time modifications to the text segment.
94 The linker-editor allocates the Global Offset Table and Procedure Linkage Table
95 when combining PIC object files into an image suitable for mapping into the
96 process address space.
97 It also collects all symbols that may be needed by the
98 run-time link-editor and stores these along with the image's text and data bits.
99 Another reserved symbol,
101 is used to indicate the presence of the run-time linker structures.
103 _DYNAMIC is relocated to 0, there is no need to invoke the run-time
105 If this symbol is non-zero, it points at a data structure from
106 which the location of the necessary relocation- and symbol information can
108 This is most notably used by the start-up module,
110 The _DYNAMIC structure is conventionally located at the start of the data
111 segment of the image to which it pertains.
113 The data structures supporting dynamic linking and run-time relocation
114 reside both in the text and data segments of the image they apply to.
115 The text segments contain read-only data such as symbols descriptions and
116 names, while the data segments contain the tables that need to be modified by
117 during the relocation process.
119 The _DYNAMIC symbol references a
122 .Bd -literal -offset indent
125 struct so_debug *d_debug;
127 struct section_dispatch_table *d_sdt;
129 struct ld_entry *d_entry;
132 .Bl -tag -width d_version
134 This field provides for different versions of the dynamic linking
136 The current version numbers understood by
141 .Em LD_VERSION_SUN (3) ,
145 .Em LD_VERSION_BSD (8) ,
146 which has been in use since
151 dependent data structure.
153 this field provides debuggers with a hook to access symbol tables of shared
154 objects loaded as a result of the actions of the run-time link-editor.
158 .Fa section_dispatch_table
159 structure is the main
161 table, containing offsets into the image's segments where various symbol
162 and relocation information is located.
163 .Bd -literal -offset indent
164 struct section_dispatch_table {
165 struct so_map *sdt_loaded;
182 .Bl -tag -width sdt_filler1
184 A pointer to the first link map loaded (see below). This field is set by
187 The start of a (linked) list of shared object descriptors needed by
191 Deprecated (used by SunOS to specify library search rules).
193 The location of the Global Offset Table within this image.
195 The location of the Procedure Linkage Table within this image.
197 The location of an array of
202 specifying run-time relocations.
204 The location of the hash table for fast symbol lookup in this object's
207 The location of the symbol table.
211 The number of buckets in
214 The location of the symbol string table that goes with
217 The size of the string table.
219 The size of the object's text segment.
221 The size of the Procedure Linkage Table.
226 structure describes a shared object that is needed
227 to complete the link edit process of the object containing it.
228 A list of such objects
234 in the section_dispatch_table structure.
235 .Bd -literal -offset indent
238 u_int sod_library : 1,
246 .Bl -tag -width sod_library
248 The offset in the text segment of a string describing this link object.
252 specifies a library that is to be searched for by
255 is obtained by searching a set of directories
258 for a shared object matching
259 .Em lib\&<sod_name>\&.so.n.m .
262 should point at a full path name for the desired shared object.
264 Specifies the major version number of the shared object to load.
266 Specifies the preferred minor version number of the shared object to load.
269 The run-time link-editor maintains a list of structures called
271 to keep track of all shared objects loaded into a process' address space.
272 These structures are only used at run-time and do not occur within
273 the text or data segment of an executable or shared library.
274 .Bd -literal -offset indent
278 struct so_map *som_next;
282 struct _dynamic *som_dynamic;
286 .Bl -tag -width som_dynamic
288 The address at which the shared object associated with this link map has
291 The full path name of the loaded object.
293 Pointer to the next link map.
297 structure that was responsible for loading this shared object.
299 Tossed out in later versions of the run-time linker.
301 Set if (some portion of) this object's text segment is currently writable.
303 Pointer to this object's
307 Hook for attaching private data maintained by the run-time link-editor.
310 Symbol description with size.
313 structure with one field
316 Used to convey size information on items in the data segment
318 An array of these lives in the shared object's
319 text segment and is addressed by the
322 .Fa section_dispatch_table .
323 .Bd -literal -offset indent
327 #define nz_un nlist.n_un
328 #define nz_strx nlist.n_un.n_strx
329 #define nz_name nlist.n_un.n_name
330 #define nz_type nlist.n_type
331 #define nz_value nlist.n_value
332 #define nz_desc nlist.n_desc
333 #define nz_other nlist.n_other
336 .Bl -tag -width nz_size
341 The size of the data represented by this symbol.
344 A hash table is included within the text segment of shared object
345 to facilitate quick lookup of symbols during run-time link-editing.
349 .Fa section_dispatch_table
350 structure points at an array of
353 .Bd -literal -offset indent
355 int rh_symbolnum; /* symbol number */
356 int rh_next; /* next hash entry */
360 .Bl -tag -width rh_symbolnum
362 The index of the symbol in the shared object's symbol table (as given by the
366 In case of collisions, this field is the offset of the next entry in this
368 It is zero for the last bucket element.
372 structure is used to keep track of run-time allocated commons
373 and data items copied from shared objects.
374 These items are kept on linked list
375 and is exported through the
379 structure (see below) for use by debuggers.
380 .Bd -literal -offset indent
382 struct nzlist *rt_sp;
383 struct rt_symbol *rt_next;
384 struct rt_symbol *rt_link;
386 struct so_map *rt_smp;
390 .Bl -tag -width rt_scraddr
392 The symbol description.
394 Virtual address of next rt_symbol.
400 Location of the source of initialized data within a shared object.
402 The shared object which is the original source of the data that this
403 run-time symbol describes.
408 structure is used by debuggers to gain knowledge of any shared objects
409 that have been loaded in the process's address space as a result of run-time
411 Since the run-time link-editor runs as a part of process
412 initialization, a debugger that wishes to access symbols from shared objects
413 can only do so after the link-editor has been called from crt0.
414 A dynamically linked binary contains a
416 structure which can be located by means of the
420 .Bd -literal -offset indent
427 struct rt_symbol *dd_cc;
431 .Bl -tag -width dd_in_debugger
433 Version number of this interface.
434 .It Fa dd_in_debugger
435 Set by the debugger to indicate to the run-time linker that the program is
436 run under control of a debugger.
438 Set by the run-time linker whenever it adds symbols by loading shared objects.
440 The address where a breakpoint will be set by the run-time linker to
441 divert control to the debugger.
442 This address is determined by the start-up
445 to be some convenient place before the call to _main.
447 Contains the original instruction that was at
449 The debugger is expected to put this instruction back before continuing the
452 A pointer to the linked list of run-time allocated symbols that the debugger
453 may be interested in.
458 structure defines a set of service routines within
462 .\" for more information.
463 .Bd -literal -offset indent
465 void *(*dlopen)(char *, int);
466 int (*dlclose)(void *);
467 void *(*dlsym)(void *, char *);
468 char *(*dlerror)(void);
474 structure defines the interface between the start-up code in crt0 and
476 .Bd -literal -offset indent
481 struct _dynamic *crt_dp;
486 struct ld_entry *crt_ldentry;
488 #define CRT_VERSION_SUN 1
489 #define CRT_VERSION_BSD_2 2
490 #define CRT_VERSION_BSD_3 3
491 #define CRT_VERSION_BSD_4 4
493 .Bl -tag -width crt_dzfd
495 The virtual address at which
499 On SunOS systems, this field contains an open file descriptor to
501 used to get demand paged zeroed pages.
504 systems it contains -1.
506 Contains an open file descriptor that was used by crt0 to load
513 A pointer to the environment strings.
515 The address at which a breakpoint will be placed by the run-time linker
516 if the main program is run by a debugger.
520 The name of the main program as determined by crt0 (CRT_VERSION_BSD3 only).
522 The path of the run-time linker as mapped by crt0 (CRT_VERSION_BSD4 only).
529 structures define the layout of the library hints, normally found in
530 .Dq Pa /var/run/ld-elf.so.hints ,
533 to quickly locate the shared object images in the
535 The organization of the hints file is not unlike that of an
537 object file, in that it contains a header determining the offset and size
538 of a table of fixed sized hash buckets and a common string pool.
539 .Bd -literal -offset indent
540 struct hints_header {
542 #define HH_MAGIC 011421044151
544 #define LD_HINTS_VERSION_1 1
552 .Bl -tag -width hh_strtab_sz
554 Hints file magic number.
556 Interface version number.
558 Offset of hash table.
560 Offset of string table.
564 Maximum usable offset in hints file.
567 .Bd -literal -offset indent
569 * Hash table element in hints file.
571 struct hints_bucket {
574 int hi_dewey[MAXDEWEY];
576 #define hi_major hi_dewey[0]
577 #define hi_minor hi_dewey[1]
581 .Bl -tag -width hi_ndewey
583 Index of the string identifying the library.
585 Index of the string representing the full path name of the library.
587 The version numbers of the shared library.
589 The number of valid entries in
592 Next bucket in case of hashing collisions.
595 Only the (GNU) C compiler currently supports the creation of shared libraries.
596 Other programming languages cannot be used.