1 .\" Copyright (c) 1999 Jeroen Ruigrok van der Werven
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.
13 .\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS'' AND
14 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
15 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
16 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE
17 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
18 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
19 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
20 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
21 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
22 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
25 .\" $FreeBSD: src/share/man/man5/elf.5,v 1.36 2007/09/08 08:12:31 jkoshy Exp $
26 .\" $DragonFly: src/share/man/man5/elf.5,v 1.12 2008/08/30 17:01:17 swildner Exp $
33 .Nd format of ELF executable binary files
39 defines the format of ELF executable binary files.
40 Amongst these files are
41 normal executable files, relocatable object files, core files and shared
44 An executable file using the ELF file format consists of an ELF header,
45 followed by a program header table or a section header table, or both.
46 The ELF header is always at offset zero of the file.
48 table and the section header table's offset in the file are defined in the
50 The two tables describe the rest of the particularities of
53 Applications which wish to process ELF binary files for their native
54 architecture only should include
57 These applications should need to refer to
58 all the types and structures by their generic names
62 Applications written this way can be compiled on any architecture,
63 regardless whether the host is 32-bit or 64-bit.
65 Should an application need to process ELF files of an unknown
66 architecture then the application needs to include both
72 Furthermore, all types and structures need to be identified by either
76 The macros need to be identified by
81 Whatever the system's architecture is, it will always include
84 .In sys/elf_generic.h .
86 These header files describe the above mentioned headers as C structures
87 and also include structures for dynamic sections, relocation sections and
90 The following types are being used for 32-bit architectures:
91 .Bd -literal -offset indent
92 Elf32_Addr Unsigned 32-bit program address
93 Elf32_Half Unsigned 16-bit field
94 Elf32_Off Unsigned 32-bit file offset
95 Elf32_Sword Signed 32-bit field or integer
96 Elf32_Word Unsigned 32-bit field or integer
97 Elf32_Size Unsigned object size
100 For 64-bit architectures we have the following types:
101 .Bd -literal -offset indent
102 Elf64_Addr Unsigned 64-bit program address
103 Elf64_Half Unsigned 16-bit field
104 Elf64_Lword Unsigned 64-bit field
105 Elf64_Off Unsigned 64-bit file offset
106 Elf64_Sword Signed 32-bit field
107 Elf64_Sxword Signed 64-bit field or integer
108 Elf64_Word Unsigned 32-bit field
109 Elf64_Xword Unsigned 64-bit field or integer
110 Elf64_Size Unsigned object size
113 All data structures that the file format defines follow the
115 size and alignment guidelines for the relevant class.
117 data structures contain explicit padding to ensure 4-byte alignment
118 for 4-byte objects, to force structure sizes to a multiple of 4, etc.
120 The ELF header is described by the type Elf32_Ehdr or Elf64_Ehdr:
121 .Bd -literal -offset indent
123 unsigned char e_ident[EI_NIDENT];
125 Elf32_Half e_machine;
126 Elf32_Word e_version;
132 Elf32_Half e_phentsize;
134 Elf32_Half e_shentsize;
136 Elf32_Half e_shstrndx;
139 .Bd -literal -offset indent
141 unsigned char e_ident[EI_NIDENT];
143 Elf64_Half e_machine;
144 Elf64_Word e_version;
150 Elf64_Half e_phentsize;
152 Elf64_Half e_shentsize;
154 Elf64_Half e_shstrndx;
158 The fields have the following meanings:
160 .Bl -tag -width ".Fa e_phentsize" -compact -offset indent
162 This array of bytes specifies to interpret the file,
163 independent of the processor or the file's remaining contents.
164 Within this array everything is named by macros, which start with
167 and may contain values which start with the prefix
169 The following macros are defined:
171 .Bl -tag -width ".Dv EI_ABIVERSION" -compact
173 The first byte of the magic number.
174 It must be filled with
177 The second byte of the magic number.
178 It must be filled with
181 The third byte of the magic number.
182 It must be filled with
185 The fourth byte of the magic number.
186 It must be filled with
189 The fifth byte identifies the architecture for this binary:
191 .Bl -tag -width ".Dv ELFCLASSNONE" -compact
193 This class is invalid.
195 This defines the 32-bit architecture.
196 It supports machines with files
197 and virtual address spaces up to 4 Gigabytes.
199 This defines the 64-bit architecture.
202 The sixth byte specifies the data encoding of the processor-specific
204 Currently these encodings are supported:
206 .Bl -tag -width ".Dv ELFDATA2LSB" -compact
210 Two's complement, little-endian.
212 Two's complement, big-endian.
215 The version number of the ELF specification:
217 .Bl -tag -width ".Dv EV_CURRENT" -compact
224 This byte identifies the operating system
225 and ABI to which the object is targeted.
226 Some fields in other ELF structures have flags
227 and values that have platform specific meanings;
228 the interpretation of those fields is determined by the value of this byte.
229 The following values are currently defined:
231 .Bl -tag -width ".Dv ELFOSABI_STANDALONE" -compact
236 HP-UX operating system ABI.
237 .It Dv ELFOSABI_NETBSD
239 operating system ABI.
240 .It Dv ELFOSABI_LINUX
241 GNU/Linux operating system ABI.
243 GNU/Hurd operating system ABI.
244 .It Dv ELFOSABI_86OPEN
245 86Open Common IA32 ABI.
246 .It Dv ELFOSABI_SOLARIS
247 Solaris operating system ABI.
248 .It Dv ELFOSABI_MONTEREY
249 Monterey project ABI.
251 IRIX operating system ABI.
252 .It Dv ELFOSABI_FREEBSD
254 operating system ABI.
255 .It Dv ELFOSABI_TRU64
258 operating system ABI.
260 ARM architecture ABI.
261 .It Dv ELFOSABI_STANDALONE
262 Standalone (embedded) ABI.
265 This byte identifies the version of the ABI
266 to which the object is targeted.
267 This field is used to distinguish among incompatible versions of an ABI.
268 The interpretation of this version number
269 is dependent on the ABI identified by the
272 Applications conforming to this specification use the value 0.
275 These bytes are reserved and set to zero.
277 which read them should ignore them.
278 The value for EI_PAD will change in
279 the future if currently unused bytes are given meanings.
287 This member of the structure identifies the object file type:
289 .Bl -tag -width ".Dv ET_NONE" -compact
303 This member specifies the required architecture for an individual file:
305 .Bl -tag -width ".Dv EM_MIPS_RS4_BE" -compact
311 Sun Microsystems SPARC.
321 MIPS RS3000 (big-endian only).
322 .It Dv EM_MIPS_RS4_BE
323 MIPS RS4000 (big-endian only).
325 SPARC v9 64-bit unofficial.
335 This member identifies the file version:
337 .Bl -tag -width ".Dv EV_CURRENT" -compact
344 This member gives the virtual address to which the system first transfers
345 control, thus starting the process.
346 If the file has no associated entry
347 point, this member holds zero.
349 This member holds the program header table's file offset in bytes.
351 the file has no program header table, this member holds zero.
353 This member holds the section header table's file offset in bytes.
355 file has no section header table this member holds zero.
357 This member holds processor-specific flags associated with the file.
358 Flag names take the form EF_`machine_flag'.
359 Currently no flags have been defined.
361 This member holds the ELF header's size in bytes.
363 This member holds the size in bytes of one entry in the file's program header
364 table; all entries are the same size.
366 This member holds the number of entries in the program header
372 gives the table's size
374 If a file has no program header,
376 holds the value zero.
378 This member holds a sections header's size in bytes.
379 A section header is one
380 entry in the section header table; all entries are the same size.
382 This member holds the number of entries in the section header table.
388 gives the section header table's size in bytes.
389 If a file has no section
392 holds the value of zero.
394 This member holds the section header table index of the entry associated
395 with the section name string table.
396 If the file has no section name string
397 table, this member holds the value
400 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
402 This value marks an undefined, missing, irrelevant, or otherwise meaningless
404 For example, a symbol
406 relative to section number
408 is an undefined symbol.
410 This value specifies the lower bound of the range of reserved indexes.
412 This value up to and including
414 are reserved for processor-specific semantics.
416 This value down to and including
418 are reserved for processor-specific semantics.
420 This value specifies absolute values for the corresponding reference.
422 example, symbols defined relative to section number
424 have absolute values and are not affected by relocation.
426 Symbols defined relative to this section are common symbols, such as Fortran
427 COMMON or unallocated C external variables.
429 This value specifies the upper bound of the range of the range of reserved
434 inclusive; the values do
435 not reference the section header table.
436 That is, the section header table
439 contain entries for the reserved indices.
443 An executable or shared object file's program header table is an array of
444 structures, each describing a segment or other information the system needs
445 to prepare the program for execution.
450 Program headers are meaningful only for executable and shared object files.
451 A file specifies its own program header size with the ELF header's
456 As with the Elf executable header, the program header
457 also has different versions depending on the architecture:
458 .Bd -literal -offset indent
470 .Bd -literal -offset indent
477 Elf64_Xword p_filesz;
483 The main difference between the 32-bit and the 64-bit program header lies
484 only in the location of a
486 member in the total struct.
488 .Bl -tag -width ".Fa p_offset" -compact -offset indent
492 struct tells what kind of segment this array
493 element describes or how to interpret the array element's information.
495 .Bl -tag -width ".Dv PT_DYNAMIC" -compact
497 The array element is unused and the other members' values are undefined.
498 This lets the program header have ignored entries.
500 The array element specifies a loadable segment, described by
504 The bytes from the file are mapped to the beginning of the memory
506 If the segment's memory size
508 is larger than the file size
512 bytes are defined to hold the value 0 and to follow the segment's
514 The file size may not be larger than the memory size.
515 Loadable segment entries in the program header table appear in ascending
520 The array element specifies dynamic linking information.
522 The array element specifies the location and size of a null-terminated
523 path name to invoke as an interpreter.
524 This segment type is meaningful
525 only for executable files (though it may occur for shared objects).
526 However, it may not occur more than once in a file.
527 If it is present it must precede
528 any loadable segment entry.
530 The array element specifies the location and size for auxiliary information.
532 This segment type is reserved but has unspecified semantics.
534 contain an array element of this type do not conform to the ABI.
536 The array element, if present, specifies the location and size of the program
537 header table itself, both in the file and in the memory image of the program.
538 This segment type may not occur more than once in a file.
540 only occur if the program header table is part of the memory image of the
542 If it is present it must precede any loadable segment entry.
544 This value up to and including
546 are reserved for processor-specific semantics.
548 This value down to and including
550 are reserved for processor-specific semantics.
554 This member holds the offset from the beginning of the file at which
555 the first byte of the segment resides.
557 This member holds the virtual address at which the first byte of the
558 segment resides in memory.
560 On systems for which physical addressing is relevant, this member is
561 reserved for the segment's physical address.
565 not used and must be zero.
567 This member holds the number of bytes in the file image of the segment.
570 This member holds the number of bytes in the memory image of the segment.
573 This member holds flags relevant to the segment:
575 .Bl -tag -width ".Dv PF_X" -compact
577 An executable segment.
584 A text segment commonly has the flags
588 A data segment commonly has
594 This member holds the value to which the segments are aligned in memory
596 Loadable process segments must have congruent values for
600 modulo the page size.
601 Values of zero and one mean no alignment is required.
604 should be a positive, integral power of two, and
612 An file's section header table lets one locate all the file's sections.
614 section header table is an array of
621 member gives the byte offset from the beginning of the file to the section
624 holds the number of entries the section header table contains.
626 holds the size in bytes of each entry.
628 A section header table index is a subscript into this array.
630 header table indices are reserved.
631 An object file does not have sections for
632 these special indices:
634 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
636 This value marks an undefined, missing, irrelevant, or otherwise meaningless
639 This value specifies the lower bound of the range of reserved indices.
641 This value up to and including
643 are reserved for processor-specific semantics.
645 This value down to and including
647 are reserved for processor-specific semantics.
649 This value specifies absolute values for the corresponding reference.
651 example, symbols defined relative to section number
653 have absolute values and are not affected by relocation.
655 Symbols defined relative to this section are common symbols, such as FORTRAN
656 COMMON or unallocated C external variables.
658 This value specifies the upper bound of the range of reserved indices.
660 system reserves indices between
665 The section header table does not contain entries for the
669 The section header has the following structure:
670 .Bd -literal -offset indent
680 Elf32_Size sh_addralign;
681 Elf32_Size sh_entsize;
684 .Bd -literal -offset indent
688 Elf64_Xword sh_flags;
694 Elf64_Xword sh_addralign;
695 Elf64_Xword sh_entsize;
699 .Bl -tag -width ".Fa sh_addralign" -compact
701 This member specifies the name of the section.
702 Its value is an index
703 into the section header string table section, giving the location of
704 a null-terminated string.
706 This member categorizes the section's contents and semantics.
708 .Bl -tag -width ".Dv SHT_PROGBITS" -compact
710 This value marks the section header as inactive.
712 have an associated section.
713 Other members of the section header
714 have undefined values.
716 The section holds information defined by the program, whose
717 format and meaning are determined solely by the program.
719 This section holds a symbol table.
722 provides symbols for link editing, though it may also be used
724 As a complete symbol table, it may contain
725 many symbols unnecessary for dynamic linking.
731 This section holds a string table.
732 An object file may have multiple
733 string table sections.
735 This section holds relocation entries with explicit addends, such
738 for the 32-bit class of object files.
739 An object may have multiple
742 This section holds a symbol hash table.
743 All object participating in
744 dynamic linking must contain a symbol hash table.
746 have only one hash table.
748 This section holds information for dynamic linking.
750 have only one dynamic section.
752 This section holds information that marks the file in some way.
754 A section of this type occupies no space in the file but otherwise
757 Although this section contains no bytes, the
759 member contains the conceptual file offset.
761 This section holds relocation offsets without explicit addends, such
764 for the 32-bit class of object files.
765 An object file may have multiple
768 This section is reserved but has unspecified semantics.
770 This section holds a minimal set of dynamic linking symbols.
772 object file can also contain a
776 This value up to and including
778 are reserved for processor-specific semantics.
780 This value down to and including
782 are reserved for processor-specific semantics.
784 This value specifies the lower bound of the range of indices reserved for
785 application programs.
787 This value specifies the upper bound of the range of indices reserved for
788 application programs.
789 Section types between
793 may be used by the application, without conflicting with current or future
794 system-defined section types.
798 Sections support one-bit flags that describe miscellaneous attributes.
799 If a flag bit is set in
804 Otherwise, the attribute is
807 Undefined attributes are set to zero.
809 .Bl -tag -width ".Dv SHF_EXECINSTR" -compact
811 This section contains data that should be writable during process
814 The section occupies memory during process execution.
816 sections do not reside in the memory image of an object file.
818 attribute is off for those sections.
820 The section contains executable machine instructions.
822 All bits included in this mask are reserved for processor-specific
827 If the section will appear in the memory image of a process, this member
828 holds the address at which the section's first byte should reside.
829 Otherwise, the member contains zero.
831 This member's value holds the byte offset from the beginning of the file
832 to the first byte in the section.
835 occupies no space in the file, and its
837 member locates the conceptual placement in the file.
839 This member holds the section's size in bytes.
840 Unless the section type
848 may have a non-zero size, but it occupies no space in the file.
850 This member holds a section header table index link, whose interpretation
851 depends on the section type.
853 This member holds extra information, whose interpretation depends on the
856 Some sections have address alignment constraints.
858 doubleword, the system must ensure doubleword alignment for the entire
860 That is, the value of
862 must be congruent to zero, modulo the value of
864 Only zero and positive integral powers of two are allowed.
866 or one mean the section has no alignment constraints.
868 Some sections hold a table of fixed-sized entries, such as a symbol table.
869 For such a section, this member gives the size in bytes for each entry.
870 This member contains zero if the section does not hold a table of
874 Various sections hold program and control information:
875 .Bl -tag -width ".Sy .shstrtab" -compact
877 (Block Started by Symbol)
878 This section holds uninitialized data that contributes to the program's
880 By definition, the system initializes the data with zeros
881 when the program begins to run.
882 This section is of type
884 The attributes types are
889 This section holds version control information.
890 This section is of type
892 No attribute types are used.
894 This section holds initialized data that contribute to the program's
896 This section is of type
898 The attribute types are
903 This section holds initialized data that contribute to the program's
905 This section is of type
907 The attribute types are
912 This section holds information for symbolic debugging.
915 This section is of type
917 No attribute types are used.
919 This section holds dynamic linking information.
920 The section's attributes
926 bit is set is processor-specific.
927 This section is of type
929 See the attributes above.
931 This section holds strings needed for dynamic linking, most commonly
932 the strings that represent the names associated with symbol table entries.
933 This section is of type
935 The attribute type used is
938 This section holds the dynamic linking symbol table.
939 This section is of type
941 The attribute used is
944 This section holds executable instructions that contribute to the process
946 When a program exits normally the system arranges to
947 execute the code in this section.
948 This section is of type
950 The attributes used are
955 This section holds the global offset table.
956 This section is of type
958 The attributes are processor-specific.
960 This section holds a symbol hash table.
961 This section is of type
963 The attribute used is
966 This section holds executable instructions that contribute to the process
968 When a program starts to run the system arranges to
969 execute the code in this section before calling the main program entry point.
970 This section is of type
972 The attributes used are
977 This section holds the pathname of a program interpreter.
979 a loadable segment that includes the section, the section's attributes will
983 Otherwise, that bit will be off.
984 This section is of type
987 This section holds line number information for symbolic debugging, which
988 describes the correspondence between the program source and the machine code.
989 The contents are unspecified.
990 This section is of type
992 No attribute types are used.
994 This section holds information in the
996 format described below.
997 This section is of type
999 No attribute types are used.
1001 This section holds the procedure linkage table.
1002 This section is of type
1004 The attributes are processor-specific.
1006 This section holds relocation information as described below.
1008 has a loadable segment that includes relocation, the section's attributes
1012 Otherwise the bit will be off.
1015 is supplied by the section to which the relocations apply.
1019 normally would have the name
1021 This section is of type
1024 This section holds relocation information as described below.
1026 has a loadable segment that includes relocation, the section's attributes
1030 Otherwise the bit will be off.
1033 is supplied by the section to which the relocations apply.
1037 normally would have the name
1039 This section is of type
1042 This section holds read-only data that typically contributes to a
1043 non-writable segment in the process image.
1044 This section is of type
1046 The attribute used is
1049 This section hold read-only data that typically contributes to a
1050 non-writable segment in the process image.
1051 This section is of type
1053 The attribute used is
1056 This section holds section names.
1057 This section is of type
1059 No attribute types are used.
1061 This section holds strings, most commonly the strings that represent the
1062 names associated with symbol table entries.
1063 If the file has a loadable
1064 segment that includes the symbol string table, the section's attributes
1068 Otherwise the bit will be off.
1069 This section is of type
1072 This section holds a symbol table.
1073 If the file has a loadable segment
1074 that includes the symbol table, the section's attributes will include
1078 Otherwise the bit will be off.
1079 This section is of type
1082 This section holds the
1084 or executable instructions, of a program.
1085 This section is of type
1087 The attributes used are
1093 String table sections hold null-terminated character sequences, commonly
1095 The object file uses these strings to represent symbol
1097 One references a string as an index into the string
1099 The first byte, which is index zero, is defined to hold
1101 Similarly, a string table's last byte is defined to
1102 hold a null character, ensuring null termination for all strings.
1104 An object file's symbol table holds information needed to locate and
1105 relocate a program's symbolic definitions and references.
1107 index is a subscript into this array.
1108 .Bd -literal -offset indent
1111 Elf32_Addr st_value;
1113 unsigned char st_info;
1114 unsigned char st_other;
1115 Elf32_Half st_shndx;
1118 .Bd -literal -offset indent
1121 unsigned char st_info;
1122 unsigned char st_other;
1123 Elf64_Half st_shndx;
1124 Elf64_Addr st_value;
1125 Elf64_Xword st_size;
1129 .Bl -tag -width ".Fa st_value" -compact
1131 This member holds an index into the object file's symbol string table,
1132 which holds character representations of the symbol names.
1134 is non-zero, it represents a string table index that gives the symbol
1136 Otherwise, the symbol table has no name.
1138 This member gives the value of the associated symbol.
1140 Many symbols have associated sizes.
1141 This member holds zero if the symbol
1142 has no size or an unknown size.
1144 This member specifies the symbol's type and binding attributes:
1146 .Bl -tag -width ".Dv STT_SECTION" -compact
1148 The symbol's type is not defined.
1150 The symbol is associated with a data object.
1152 The symbol is associated with a function or other executable code.
1154 The symbol is associated with a section.
1155 Symbol table entries of
1156 this type exist primarily for relocation and normally have
1160 By convention the symbol's name gives the name of the source file
1161 associated with the object file.
1164 bindings, its section index is
1166 and it precedes the other
1168 symbols of the file, if it is present.
1170 This value up to and including
1172 are reserved for processor-specific semantics.
1174 This value down to and including
1176 are reserved for processor-specific semantics.
1179 .Bl -tag -width ".Dv STB_GLOBAL" -compact
1181 Local symbols are not visible outside the object file containing their
1183 Local symbols of the same name may exist in multiple file
1184 without interfering with each other.
1186 Global symbols are visible to all object files being combined.
1188 definition of a global symbol will satisfy another file's undefined
1189 reference to the same symbol.
1191 Weak symbols resemble global symbols, but their definitions have lower
1194 This value up to and including
1196 are reserved for processor-specific semantics.
1198 This value down to and including
1200 are reserved for processor-specific semantics.
1202 There are macros for packing and unpacking the binding and type fields:
1204 .Bl -tag -width ".Fn ELF32_ST_INFO bind type" -compact
1206 .Fn ELF32_ST_BIND info
1209 .Fn ELF64_ST_BIND info
1210 extract a binding from an
1214 .Fn ELF64_ST_TYPE info
1217 .Fn ELF32_ST_TYPE info
1218 extract a type from an
1222 .Fn ELF32_ST_INFO bind type
1225 .Fn ELF64_ST_INFO bind type
1226 convert a binding and a type into an
1233 This member currently holds zero and has no defined meaning.
1235 Every symbol table entry is
1237 in relation to some section.
1238 This member holds the relevant section
1242 Relocation is the process of connecting symbolic references with
1243 symbolic definitions.
1244 Relocatable files must have information that
1245 describes how to modify their section contents, thus allowing executable
1246 and shared object files to hold the right information for a process'
1248 Relocation entries are these data.
1250 Relocation structures that do not need an addend:
1251 .Bd -literal -offset indent
1253 Elf32_Addr r_offset;
1257 .Bd -literal -offset indent
1259 Elf64_Addr r_offset;
1264 Relocation structures that need an addend:
1265 .Bd -literal -offset indent
1267 Elf32_Addr r_offset;
1269 Elf32_Sword r_addend;
1272 .Bd -literal -offset indent
1274 Elf64_Addr r_offset;
1276 Elf64_Sxword r_addend;
1280 .Bl -tag -width ".Fa r_offset" -compact
1282 This member gives the location at which to apply the relocation action.
1283 For a relocatable file, the value is the byte offset from the beginning
1284 of the section to the storage unit affected by the relocation.
1286 executable file or shared object, the value is the virtual address of
1287 the storage unit affected by the relocation.
1289 This member gives both the symbol table index with respect to which the
1290 relocation must be made and the type of relocation to apply.
1292 types are processor-specific.
1293 When the text refers to a relocation
1294 entry's relocation type or symbol table index, it means the result of
1296 .Fn ELF[32|64]_R_TYPE
1298 .Fn ELF[32|64]_R_SYM ,
1299 respectively to the entry's
1303 This member specifies a constant addend used to compute the value to be
1304 stored into the relocatable field.
1316 .%B Elf-64 Object File Format
1319 .%A Santa Cruz Operation
1320 .%B System V Application Binary Interface
1323 .%A Unix System Laboratories
1325 .%B "Executable and Linking Format (ELF)"
1328 The ELF header files made their appearance in
1330 ELF in itself first appeared in
1332 The ELF format is an adopted standard.
1334 This manual page was written by
1335 .An Jeroen Ruigrok van der Werven
1336 .Aq asmodai@FreeBSD.org
1337 with inspiration from BSDi's