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.6.2.8 2001/12/17 11:30:13 ru Exp $
26 .\" $DragonFly: src/share/man/man5/elf.5,v 1.8 2007/12/15 12:04:42 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
111 Elf64_Quarter Unsigned quarterword field
114 All data structures that the file format defines follow the
116 size and alignment guidelines for the relevant class.
118 data structures contain explicit padding to ensure 4-byte alignment
119 for 4-byte objects, to force structure sizes to a multiple of 4, etc.
121 The ELF header is described by the type Elf32_Ehdr or Elf64_Ehdr:
122 .Bd -literal -offset indent
124 unsigned char e_ident[EI_NIDENT];
126 Elf32_Half e_machine;
127 Elf32_Word e_version;
133 Elf32_Half e_phentsize;
135 Elf32_Half e_shentsize;
137 Elf32_Half e_shstrndx;
141 .Bd -literal -offset indent
143 unsigned char e_ident[EI_NIDENT];
144 Elf64_Quarter e_type;
145 Elf64_Quarter e_machine;
146 Elf64_Half e_version;
151 Elf64_Quarter e_ehsize;
152 Elf64_Quarter e_phentsize;
153 Elf64_Quarter e_phnum;
154 Elf64_Quarter e_shentsize;
155 Elf64_Quarter e_shnum;
156 Elf64_Quarter e_shstrndx;
160 The fields have the following meanings:
162 .Bl -tag -width ".Fa e_phentsize" -compact -offset indent
164 This array of bytes specifies to interpret the file,
165 independent of the processor or the file's remaining contents.
166 Within this array everything is named by macros, which start with
169 and may contain values which start with the prefix
171 The following macros are defined:
173 .Bl -tag -width ".Dv EI_ABIVERSION" -compact
175 The first byte of the magic number.
176 It must be filled with
179 The second byte of the magic number.
180 It must be filled with
183 The third byte of the magic number.
184 It must be filled with
187 The fourth byte of the magic number.
188 It must be filled with
191 The fifth byte identifies the architecture for this binary:
193 .Bl -tag -width ".Dv ELFCLASSNONE" -compact
195 This class is invalid.
197 This defines the 32-bit architecture.
198 It supports machines with files
199 and virtual address spaces up to 4 Gigabytes.
201 This defines the 64-bit architecture.
204 The sixth byte specifies the data encoding of the processor-specific
206 Currently these encodings are supported:
208 .Bl -tag -width ".Dv ELFDATA2LSB" -compact
212 Two's complement, little-endian.
214 Two's complement, big-endian.
217 The version number of the ELF specification:
219 .Bl -tag -width ".Dv EV_CURRENT" -compact
226 This byte identifies the operating system
227 and ABI to which the object is targeted.
228 Some fields in other ELF structures have flags
229 and values that have platform specific meanings;
230 the interpretation of those fields is determined by the value of this byte.
231 The following values are currently defined:
233 .Bl -tag -width ".Dv ELFOSABI_STANDALONE" -compact
238 HP-UX operating system ABI.
239 .It Dv ELFOSABI_NETBSD
241 operating system ABI.
242 .It Dv ELFOSABI_LINUX
243 GNU/Linux operating system ABI.
245 GNU/Hurd operating system ABI.
246 .It Dv ELFOSABI_86OPEN
247 86Open Common IA32 ABI.
248 .It Dv ELFOSABI_SOLARIS
249 Solaris operating system ABI.
250 .It Dv ELFOSABI_MONTEREY
251 Monterey project ABI.
253 IRIX operating system ABI.
254 .It Dv ELFOSABI_FREEBSD
256 operating system ABI.
257 .It Dv ELFOSABI_TRU64
260 operating system ABI.
262 ARM architecture ABI.
263 .It Dv ELFOSABI_STANDALONE
264 Standalone (embedded) ABI.
267 This byte identifies the version of the ABI
268 to which the object is targeted.
269 This field is used to distinguish among incompatible versions of an ABI.
270 The interpretation of this version number
271 is dependent on the ABI identified by the
274 Applications conforming to this specification use the value 0.
277 These bytes are reserved and set to zero.
279 which read them should ignore them.
280 The value for EI_PAD will change in
281 the future if currently unused bytes are given meanings.
289 This member of the structure identifies the object file type:
291 .Bl -tag -width ".Dv ET_NONE" -compact
305 This member specifies the required architecture for an individual file:
307 .Bl -tag -width ".Dv EM_MIPS_RS4_BE" -compact
313 Sun Microsystems SPARC.
323 MIPS RS3000 (big-endian only).
324 .It Dv EM_MIPS_RS4_BE
325 MIPS RS4000 (big-endian only).
327 SPARC v9 64-bit unofficial.
337 This member identifies the file version:
339 .Bl -tag -width ".Dv EV_CURRENT" -compact
346 This member gives the virtual address to which the system first transfers
347 control, thus starting the process.
348 If the file has no associated entry
349 point, this member holds zero.
351 This member holds the program header table's file offset in bytes.
353 the file has no program header table, this member holds zero.
355 This member holds the section header table's file offset in bytes.
357 file has no section header table this member holds zero.
359 This member holds processor-specific flags associated with the file.
360 Flag names take the form EF_`machine_flag'.
361 Currently no flags have been defined.
363 This member holds the ELF header's size in bytes.
365 This member holds the size in bytes of one entry in the file's program header
366 table; all entries are the same size.
368 This member holds the number of entries in the program header
374 gives the table's size
376 If a file has no program header,
378 holds the value zero.
380 This member holds a sections header's size in bytes.
381 A section header is one
382 entry in the section header table; all entries are the same size.
384 This member holds the number of entries in the section header table.
390 gives the section header table's size in bytes.
391 If a file has no section
394 holds the value of zero.
396 This member holds the section header table index of the entry associated
397 with the section name string table.
398 If the file has no section name string
399 table, this member holds the value
402 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
404 This value marks an undefined, missing, irrelevant, or otherwise meaningless
406 For example, a symbol
408 relative to section number
410 is an undefined symbol.
412 This value specifies the lower bound of the range of reserved indexes.
414 This value up to and including
416 are reserved for processor-specific semantics.
418 This value down to and including
420 are reserved for processor-specific semantics.
422 This value specifies absolute values for the corresponding reference.
424 example, symbols defined relative to section number
426 have absolute values and are not affected by relocation.
428 Symbols defined relative to this section are common symbols, such as Fortran
429 COMMON or unallocated C external variables.
431 This value specifies the upper bound of the range of the range of reserved
436 inclusive; the values do
437 not reference the section header table.
438 That is, the section header table
441 contain entries for the reserved indices.
445 An executable or shared object file's program header table is an array of
446 structures, each describing a segment or other information the system needs
447 to prepare the program for execution.
452 Program headers are meaningful only for executable and shared object files.
453 A file specifies its own program header size with the ELF header's
458 As with the Elf executable header, the program header
459 also has different versions depending on the architecture:
461 .Bd -literal -offset indent
474 .Bd -literal -offset indent
487 The main difference between the 32-bit and the 64-bit program header lies
488 only in the location of a
490 member in the total struct.
492 .Bl -tag -width ".Fa p_offset" -compact -offset indent
496 struct tells what kind of segment this array
497 element describes or how to interpret the array element's information.
498 .Bl -tag -width ".Dv PT_DYNAMIC" -compact
501 The array element is unused and the other members' values are undefined.
502 This lets the program header have ignored entries.
504 The array element specifies a loadable segment, described by
508 The bytes from the file are mapped to the beginning of the memory
510 If the segment's memory size
512 is larger than the file size
516 bytes are defined to hold the value 0 and to follow the segment's
518 The file size may not be larger than the memory size.
519 Loadable segment entries in the program header table appear in ascending
524 The array element specifies dynamic linking information.
526 The array element specifies the location and size of a null-terminated
527 path name to invoke as an interpreter.
528 This segment type is meaningful
529 only for executable files (though it may occur for shared objects).
530 However, it may not occur more than once in a file.
531 If it is present it must precede
532 any loadable segment entry.
534 The array element specifies the location and size for auxiliary information.
536 This segment type is reserved but has unspecified semantics.
538 contain an array element of this type do not conform to the ABI.
540 The array element, if present, specifies the location and size of the program
541 header table itself, both in the file and in the memory image of the program.
542 This segment type may not occur more than once in a file.
544 only occur if the program header table is part of the memory image of the
546 If it is present it must precede any loadable segment entry.
548 This value up to and including
550 are reserved for processor-specific semantics.
552 This value down to and including
554 are reserved for processor-specific semantics.
558 This member holds the offset from the beginning of the file at which
559 the first byte of the segment resides.
561 This member holds the virtual address at which the first byte of the
562 segment resides in memory.
564 On systems for which physical addressing is relevant, this member is
565 reserved for the segment's physical address.
569 not used and must be zero.
571 This member holds the number of bytes in the file image of the segment.
574 This member holds the number of bytes in the memory image of the segment.
577 This member holds flags relevant to the segment:
579 .Bl -tag -width ".Dv PF_X" -compact
581 An executable segment.
588 A text segment commonly has the flags
592 A data segment commonly has
598 This member holds the value to which the segments are aligned in memory
600 Loadable process segments must have congruent values for
604 modulo the page size.
605 Values of zero and one mean no alignment is required.
608 should be a positive, integral power of two, and
616 An file's section header table lets one locate all the file's sections.
618 section header table is an array of
625 member gives the byte offset from the beginning of the file to the section
628 holds the number of entries the section header table contains.
630 holds the size in bytes of each entry.
632 A section header table index is a subscript into this array.
634 header table indices are reserved.
635 An object file does not have sections for
636 these special indices:
638 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
640 This value marks an undefined, missing, irrelevant, or otherwise meaningless
643 This value specifies the lower bound of the range of reserved indices.
645 This value up to and including
647 are reserved for processor-specific semantics.
649 This value down to and including
651 are reserved for processor-specific semantics.
653 This value specifies absolute values for the corresponding reference.
655 example, symbols defined relative to section number
657 have absolute values and are not affected by relocation.
659 Symbols defined relative to this section are common symbols, such as FORTRAN
660 COMMON or unallocated C external variables.
662 This value specifies the upper bound of the range of reserved indices.
664 system reserves indices between
669 The section header table does not contain entries for the
673 The section header has the following structure:
674 .Bd -literal -offset indent
684 Elf32_Size sh_addralign;
685 Elf32_Size sh_entsize;
689 .Bd -literal -offset indent
699 Elf64_Size sh_addralign;
700 Elf64_Size sh_entsize;
704 .Bl -tag -width ".Fa sh_addralign" -compact
706 This member specifies the name of the section.
707 Its value is an index
708 into the section header string table section, giving the location of
709 a null-terminated string.
711 This member categorizes the section's contents and semantics.
713 .Bl -tag -width ".Dv SHT_PROGBITS" -compact
715 This value marks the section header as inactive.
717 have an associated section.
718 Other members of the section header
719 have undefined values.
721 The section holds information defined by the program, whose
722 format and meaning are determined solely by the program.
724 This section holds a symbol table.
727 provides symbols for link editing, though it may also be used
729 As a complete symbol table, it may contain
730 many symbols unnecessary for dynamic linking.
736 This section holds a string table.
737 An object file may have multiple
738 string table sections.
740 This section holds relocation entries with explicit addends, such
743 for the 32-bit class of object files.
744 An object may have multiple
747 This section holds a symbol hash table.
748 All object participating in
749 dynamic linking must contain a symbol hash table.
751 have only one hash table.
753 This section holds information for dynamic linking.
755 have only one dynamic section.
757 This section holds information that marks the file in some way.
759 A section of this type occupies no space in the file but otherwise
762 Although this section contains no bytes, the
764 member contains the conceptual file offset.
766 This section holds relocation offsets without explicit addends, such
769 for the 32-bit class of object files.
770 An object file may have multiple
773 This section is reserved but has unspecified semantics.
775 This section holds a minimal set of dynamic linking symbols.
777 object file can also contain a
781 This value up to and including
783 are reserved for processor-specific semantics.
785 This value down to and including
787 are reserved for processor-specific semantics.
789 This value specifies the lower bound of the range of indices reserved for
790 application programs.
792 This value specifies the upper bound of the range of indices reserved for
793 application programs.
794 Section types between
798 may be used by the application, without conflicting with current or future
799 system-defined section types.
803 Sections support one-bit flags that describe miscellaneous attributes.
804 If a flag bit is set in
809 Otherwise, the attribute is
812 Undefined attributes are set to zero.
814 .Bl -tag -width ".Dv SHF_EXECINSTR" -compact
816 This section contains data that should be writable during process
819 The section occupies memory during process execution.
821 sections do not reside in the memory image of an object file.
823 attribute is off for those sections.
825 The section contains executable machine instructions.
827 All bits included in this mask are reserved for processor-specific
832 If the section will appear in the memory image of a process, this member
833 holds the address at which the section's first byte should reside.
834 Otherwise, the member contains zero.
836 This member's value holds the byte offset from the beginning of the file
837 to the first byte in the section.
840 occupies no space in the file, and its
842 member locates the conceptual placement in the file.
844 This member holds the section's size in bytes.
845 Unless the section type
853 may have a non-zero size, but it occupies no space in the file.
855 This member holds a section header table index link, whose interpretation
856 depends on the section type.
858 This member holds extra information, whose interpretation depends on the
861 Some sections have address alignment constraints.
863 doubleword, the system must ensure doubleword alignment for the entire
865 That is, the value of
867 must be congruent to zero, modulo the value of
869 Only zero and positive integral powers of two are allowed.
871 or one mean the section has no alignment constraints.
873 Some sections hold a table of fixed-sized entries, such as a symbol table.
874 For such a section, this member gives the size in bytes for each entry.
875 This member contains zero if the section does not hold a table of
879 Various sections hold program and control information:
880 .Bl -tag -width ".Sy .shstrtab" -compact
882 (Block Started by Symbol)
883 This section holds uninitialized data that contributes to the program's
885 By definition, the system initializes the data with zeros
886 when the program begins to run.
887 This section is of type
889 The attributes types are
894 This section holds version control information.
895 This section is of type
897 No attribute types are used.
899 This section holds initialized data that contribute to the program's
901 This section is of type
903 The attribute types are
908 This section holds initialized data that contribute to the program's
910 This section is of type
912 The attribute types are
917 This section holds information for symbolic debugging.
920 This section is of type
922 No attribute types are used.
924 This section holds dynamic linking information.
925 The section's attributes
931 bit is set is processor-specific.
932 This section is of type
934 See the attributes above.
936 This section holds strings needed for dynamic linking, most commonly
937 the strings that represent the names associated with symbol table entries.
938 This section is of type
940 The attribute type used is
943 This section holds the dynamic linking symbol table.
944 This section is of type
946 The attribute used is
949 This section holds executable instructions that contribute to the process
951 When a program exits normally the system arranges to
952 execute the code in this section.
953 This section is of type
955 The attributes used are
960 This section holds the global offset table.
961 This section is of type
963 The attributes are processor-specific.
965 This section holds a symbol hash table.
966 This section is of type
968 The attribute used is
971 This section holds executable instructions that contribute to the process
973 When a program starts to run the system arranges to
974 execute the code in this section before calling the main program entry point.
975 This section is of type
977 The attributes used are
982 This section holds the pathname of a program interpreter.
984 a loadable segment that includes the section, the section's attributes will
988 Otherwise, that bit will be off.
989 This section is of type
992 This section holds line number information for symbolic debugging, which
993 describes the correspondence between the program source and the machine code.
994 The contents are unspecified.
995 This section is of type
997 No attribute types are used.
999 This section holds information in the
1001 format described below.
1002 This section is of type
1004 No attribute types are used.
1006 This section holds the procedure linkage table.
1007 This section is of type
1009 The attributes are processor-specific.
1011 This section holds relocation information as described below.
1013 has a loadable segment that includes relocation, the section's attributes
1017 Otherwise the bit will be off.
1020 is supplied by the section to which the relocations apply.
1024 normally would have the name
1026 This section is of type
1029 This section holds relocation information as described below.
1031 has a loadable segment that includes relocation, the section's attributes
1035 Otherwise the bit will be off.
1038 is supplied by the section to which the relocations apply.
1042 normally would have the name
1044 This section is of type
1047 This section holds read-only data that typically contributes to a
1048 non-writable segment in the process image.
1049 This section is of type
1051 The attribute used is
1054 This section hold read-only data that typically contributes to a
1055 non-writable segment in the process image.
1056 This section is of type
1058 The attribute used is
1061 This section holds section names.
1062 This section is of type
1064 No attribute types are used.
1066 This section holds strings, most commonly the strings that represent the
1067 names associated with symbol table entries.
1068 If the file has a loadable
1069 segment that includes the symbol string table, the section's attributes
1073 Otherwise the bit will be off.
1074 This section is of type
1077 This section holds a symbol table.
1078 If the file has a loadable segment
1079 that includes the symbol table, the section's attributes will include
1083 Otherwise the bit will be off.
1084 This section is of type
1087 This section holds the
1089 or executable instructions, of a program.
1090 This section is of type
1092 The attributes used are
1098 String table sections hold null-terminated character sequences, commonly
1100 The object file uses these strings to represent symbol
1102 One references a string as an index into the string
1104 The first byte, which is index zero, is defined to hold
1106 Similarly, a string table's last byte is defined to
1107 hold a null character, ensuring null termination for all strings.
1109 An object file's symbol table holds information needed to locate and
1110 relocate a program's symbolic definitions and references.
1112 index is a subscript into this array.
1114 .Bd -literal -offset indent
1117 Elf32_Addr st_value;
1119 unsigned char st_info;
1120 unsigned char st_other;
1121 Elf32_Half st_shndx;
1125 .Bd -literal -offset indent
1128 unsigned char st_info;
1129 unsigned char st_other;
1130 Elf64_Quarter st_shndx;
1131 Elf64_Addr st_value;
1136 .Bl -tag -width ".Fa st_value" -compact
1138 This member holds an index into the object file's symbol string table,
1139 which holds character representations of the symbol names.
1141 is non-zero, it represents a string table index that gives the symbol
1143 Otherwise, the symbol table has no name.
1145 This member gives the value of the associated symbol.
1147 Many symbols have associated sizes.
1148 This member holds zero if the symbol
1149 has no size or an unknown size.
1151 This member specifies the symbol's type and binding attributes:
1153 .Bl -tag -width ".Dv STT_SECTION" -compact
1155 The symbol's type is not defined.
1157 The symbol is associated with a data object.
1159 The symbol is associated with a function or other executable code.
1161 The symbol is associated with a section.
1162 Symbol table entries of
1163 this type exist primarily for relocation and normally have
1167 By convention the symbol's name gives the name of the source file
1168 associated with the object file.
1171 bindings, its section index is
1173 and it precedes the other
1175 symbols of the file, if it is present.
1177 This value up to and including
1179 are reserved for processor-specific semantics.
1181 This value down to and including
1183 are reserved for processor-specific semantics.
1186 .Bl -tag -width ".Dv STB_GLOBAL" -compact
1188 Local symbols are not visible outside the object file containing their
1190 Local symbols of the same name may exist in multiple file
1191 without interfering with each other.
1193 Global symbols are visible to all object files being combined.
1195 definition of a global symbol will satisfy another file's undefined
1196 reference to the same symbol.
1198 Weak symbols resemble global symbols, but their definitions have lower
1201 This value up to and including
1203 are reserved for processor-specific semantics.
1205 This value down to and including
1207 are reserved for processor-specific semantics.
1209 There are macros for packing and unpacking the binding and type fields:
1211 .Bl -tag -width ".Fn ELF32_ST_INFO bind type" -compact
1213 .Fn ELF32_ST_BIND info
1216 .Fn ELF64_ST_BIND info
1217 extract a binding from an
1221 .Fn ELF64_ST_TYPE info
1224 .Fn ELF32_ST_TYPE info
1225 extract a type from an
1229 .Fn ELF32_ST_INFO bind type
1232 .Fn ELF64_ST_INFO bind type
1233 convert a binding and a type into an
1240 This member currently holds zero and has no defined meaning.
1242 Every symbol table entry is
1244 in relation to some section.
1245 This member holds the relevant section
1249 Relocation is the process of connecting symbolic references with
1250 symbolic definitions.
1251 Relocatable files must have information that
1252 describes how to modify their section contents, thus allowing executable
1253 and shared object files to hold the right information for a process'
1255 Relocation entries are these data.
1257 Relocation structures that do not need an addend:
1259 .Bd -literal -offset indent
1261 Elf32_Addr r_offset;
1265 .Bd -literal -offset indent
1267 Elf64_Addr r_offset;
1272 Relocation structures that need an addend:
1274 .Bd -literal -offset indent
1276 Elf32_Addr r_offset;
1278 Elf32_Sword r_addend;
1281 .Bd -literal -offset indent
1283 Elf64_Addr r_offset;
1289 .Bl -tag -width ".Fa r_offset" -compact
1291 This member gives the location at which to apply the relocation action.
1292 For a relocatable file, the value is the byte offset from the beginning
1293 of the section to the storage unit affected by the relocation.
1295 executable file or shared object, the value is the virtual address of
1296 the storage unit affected by the relocation.
1298 This member gives both the symbol table index with respect to which the
1299 relocation must be made and the type of relocation to apply.
1301 types are processor-specific.
1302 When the text refers to a relocation
1303 entry's relocation type or symbol table index, it means the result of
1305 .Fn ELF[32|64]_R_TYPE
1307 .Fn ELF[32|64]_R_SYM ,
1308 respectively to the entry's
1312 This member specifies a constant addend used to compute the value to be
1313 stored into the relocatable field.
1324 .%B Elf-64 Object File Format
1327 .%A Santa Cruz Operation
1328 .%B System V Application Binary Interface
1331 .%A Unix System Laboratories
1333 .%B "Executable and Linking Format (ELF)"
1336 The ELF header files made their appearance in
1338 ELF in itself first appeared in
1340 The ELF format is an adopted standard.
1342 This manual page was written by
1343 .An Jeroen Ruigrok van der Werven
1344 .Aq asmodai@FreeBSD.org
1345 with inspiration from BSDi's