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.11 2008/05/02 02:05:06 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;
140 .Bd -literal -offset indent
142 unsigned char e_ident[EI_NIDENT];
143 Elf64_Quarter e_type;
144 Elf64_Quarter e_machine;
145 Elf64_Half e_version;
150 Elf64_Quarter e_ehsize;
151 Elf64_Quarter e_phentsize;
152 Elf64_Quarter e_phnum;
153 Elf64_Quarter e_shentsize;
154 Elf64_Quarter e_shnum;
155 Elf64_Quarter e_shstrndx;
159 The fields have the following meanings:
161 .Bl -tag -width ".Fa e_phentsize" -compact -offset indent
163 This array of bytes specifies to interpret the file,
164 independent of the processor or the file's remaining contents.
165 Within this array everything is named by macros, which start with
168 and may contain values which start with the prefix
170 The following macros are defined:
172 .Bl -tag -width ".Dv EI_ABIVERSION" -compact
174 The first byte of the magic number.
175 It must be filled with
178 The second byte of the magic number.
179 It must be filled with
182 The third byte of the magic number.
183 It must be filled with
186 The fourth byte of the magic number.
187 It must be filled with
190 The fifth byte identifies the architecture for this binary:
192 .Bl -tag -width ".Dv ELFCLASSNONE" -compact
194 This class is invalid.
196 This defines the 32-bit architecture.
197 It supports machines with files
198 and virtual address spaces up to 4 Gigabytes.
200 This defines the 64-bit architecture.
203 The sixth byte specifies the data encoding of the processor-specific
205 Currently these encodings are supported:
207 .Bl -tag -width ".Dv ELFDATA2LSB" -compact
211 Two's complement, little-endian.
213 Two's complement, big-endian.
216 The version number of the ELF specification:
218 .Bl -tag -width ".Dv EV_CURRENT" -compact
225 This byte identifies the operating system
226 and ABI to which the object is targeted.
227 Some fields in other ELF structures have flags
228 and values that have platform specific meanings;
229 the interpretation of those fields is determined by the value of this byte.
230 The following values are currently defined:
232 .Bl -tag -width ".Dv ELFOSABI_STANDALONE" -compact
237 HP-UX operating system ABI.
238 .It Dv ELFOSABI_NETBSD
240 operating system ABI.
241 .It Dv ELFOSABI_LINUX
242 GNU/Linux operating system ABI.
244 GNU/Hurd operating system ABI.
245 .It Dv ELFOSABI_86OPEN
246 86Open Common IA32 ABI.
247 .It Dv ELFOSABI_SOLARIS
248 Solaris operating system ABI.
249 .It Dv ELFOSABI_MONTEREY
250 Monterey project ABI.
252 IRIX operating system ABI.
253 .It Dv ELFOSABI_FREEBSD
255 operating system ABI.
256 .It Dv ELFOSABI_TRU64
259 operating system ABI.
261 ARM architecture ABI.
262 .It Dv ELFOSABI_STANDALONE
263 Standalone (embedded) ABI.
266 This byte identifies the version of the ABI
267 to which the object is targeted.
268 This field is used to distinguish among incompatible versions of an ABI.
269 The interpretation of this version number
270 is dependent on the ABI identified by the
273 Applications conforming to this specification use the value 0.
276 These bytes are reserved and set to zero.
278 which read them should ignore them.
279 The value for EI_PAD will change in
280 the future if currently unused bytes are given meanings.
288 This member of the structure identifies the object file type:
290 .Bl -tag -width ".Dv ET_NONE" -compact
304 This member specifies the required architecture for an individual file:
306 .Bl -tag -width ".Dv EM_MIPS_RS4_BE" -compact
312 Sun Microsystems SPARC.
322 MIPS RS3000 (big-endian only).
323 .It Dv EM_MIPS_RS4_BE
324 MIPS RS4000 (big-endian only).
326 SPARC v9 64-bit unofficial.
336 This member identifies the file version:
338 .Bl -tag -width ".Dv EV_CURRENT" -compact
345 This member gives the virtual address to which the system first transfers
346 control, thus starting the process.
347 If the file has no associated entry
348 point, this member holds zero.
350 This member holds the program header table's file offset in bytes.
352 the file has no program header table, this member holds zero.
354 This member holds the section header table's file offset in bytes.
356 file has no section header table this member holds zero.
358 This member holds processor-specific flags associated with the file.
359 Flag names take the form EF_`machine_flag'.
360 Currently no flags have been defined.
362 This member holds the ELF header's size in bytes.
364 This member holds the size in bytes of one entry in the file's program header
365 table; all entries are the same size.
367 This member holds the number of entries in the program header
373 gives the table's size
375 If a file has no program header,
377 holds the value zero.
379 This member holds a sections header's size in bytes.
380 A section header is one
381 entry in the section header table; all entries are the same size.
383 This member holds the number of entries in the section header table.
389 gives the section header table's size in bytes.
390 If a file has no section
393 holds the value of zero.
395 This member holds the section header table index of the entry associated
396 with the section name string table.
397 If the file has no section name string
398 table, this member holds the value
401 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
403 This value marks an undefined, missing, irrelevant, or otherwise meaningless
405 For example, a symbol
407 relative to section number
409 is an undefined symbol.
411 This value specifies the lower bound of the range of reserved indexes.
413 This value up to and including
415 are reserved for processor-specific semantics.
417 This value down to and including
419 are reserved for processor-specific semantics.
421 This value specifies absolute values for the corresponding reference.
423 example, symbols defined relative to section number
425 have absolute values and are not affected by relocation.
427 Symbols defined relative to this section are common symbols, such as Fortran
428 COMMON or unallocated C external variables.
430 This value specifies the upper bound of the range of the range of reserved
435 inclusive; the values do
436 not reference the section header table.
437 That is, the section header table
440 contain entries for the reserved indices.
444 An executable or shared object file's program header table is an array of
445 structures, each describing a segment or other information the system needs
446 to prepare the program for execution.
451 Program headers are meaningful only for executable and shared object files.
452 A file specifies its own program header size with the ELF header's
457 As with the Elf executable header, the program header
458 also has different versions depending on the architecture:
459 .Bd -literal -offset indent
471 .Bd -literal -offset indent
484 The main difference between the 32-bit and the 64-bit program header lies
485 only in the location of a
487 member in the total struct.
489 .Bl -tag -width ".Fa p_offset" -compact -offset indent
493 struct tells what kind of segment this array
494 element describes or how to interpret the array element's information.
496 .Bl -tag -width ".Dv PT_DYNAMIC" -compact
498 The array element is unused and the other members' values are undefined.
499 This lets the program header have ignored entries.
501 The array element specifies a loadable segment, described by
505 The bytes from the file are mapped to the beginning of the memory
507 If the segment's memory size
509 is larger than the file size
513 bytes are defined to hold the value 0 and to follow the segment's
515 The file size may not be larger than the memory size.
516 Loadable segment entries in the program header table appear in ascending
521 The array element specifies dynamic linking information.
523 The array element specifies the location and size of a null-terminated
524 path name to invoke as an interpreter.
525 This segment type is meaningful
526 only for executable files (though it may occur for shared objects).
527 However, it may not occur more than once in a file.
528 If it is present it must precede
529 any loadable segment entry.
531 The array element specifies the location and size for auxiliary information.
533 This segment type is reserved but has unspecified semantics.
535 contain an array element of this type do not conform to the ABI.
537 The array element, if present, specifies the location and size of the program
538 header table itself, both in the file and in the memory image of the program.
539 This segment type may not occur more than once in a file.
541 only occur if the program header table is part of the memory image of the
543 If it is present it must precede any loadable segment entry.
545 This value up to and including
547 are reserved for processor-specific semantics.
549 This value down to and including
551 are reserved for processor-specific semantics.
555 This member holds the offset from the beginning of the file at which
556 the first byte of the segment resides.
558 This member holds the virtual address at which the first byte of the
559 segment resides in memory.
561 On systems for which physical addressing is relevant, this member is
562 reserved for the segment's physical address.
566 not used and must be zero.
568 This member holds the number of bytes in the file image of the segment.
571 This member holds the number of bytes in the memory image of the segment.
574 This member holds flags relevant to the segment:
576 .Bl -tag -width ".Dv PF_X" -compact
578 An executable segment.
585 A text segment commonly has the flags
589 A data segment commonly has
595 This member holds the value to which the segments are aligned in memory
597 Loadable process segments must have congruent values for
601 modulo the page size.
602 Values of zero and one mean no alignment is required.
605 should be a positive, integral power of two, and
613 An file's section header table lets one locate all the file's sections.
615 section header table is an array of
622 member gives the byte offset from the beginning of the file to the section
625 holds the number of entries the section header table contains.
627 holds the size in bytes of each entry.
629 A section header table index is a subscript into this array.
631 header table indices are reserved.
632 An object file does not have sections for
633 these special indices:
635 .Bl -tag -width ".Dv SHN_LORESERVE" -compact
637 This value marks an undefined, missing, irrelevant, or otherwise meaningless
640 This value specifies the lower bound of the range of reserved indices.
642 This value up to and including
644 are reserved for processor-specific semantics.
646 This value down to and including
648 are reserved for processor-specific semantics.
650 This value specifies absolute values for the corresponding reference.
652 example, symbols defined relative to section number
654 have absolute values and are not affected by relocation.
656 Symbols defined relative to this section are common symbols, such as FORTRAN
657 COMMON or unallocated C external variables.
659 This value specifies the upper bound of the range of reserved indices.
661 system reserves indices between
666 The section header table does not contain entries for the
670 The section header has the following structure:
671 .Bd -literal -offset indent
681 Elf32_Size sh_addralign;
682 Elf32_Size sh_entsize;
685 .Bd -literal -offset indent
695 Elf64_Size sh_addralign;
696 Elf64_Size sh_entsize;
700 .Bl -tag -width ".Fa sh_addralign" -compact
702 This member specifies the name of the section.
703 Its value is an index
704 into the section header string table section, giving the location of
705 a null-terminated string.
707 This member categorizes the section's contents and semantics.
709 .Bl -tag -width ".Dv SHT_PROGBITS" -compact
711 This value marks the section header as inactive.
713 have an associated section.
714 Other members of the section header
715 have undefined values.
717 The section holds information defined by the program, whose
718 format and meaning are determined solely by the program.
720 This section holds a symbol table.
723 provides symbols for link editing, though it may also be used
725 As a complete symbol table, it may contain
726 many symbols unnecessary for dynamic linking.
732 This section holds a string table.
733 An object file may have multiple
734 string table sections.
736 This section holds relocation entries with explicit addends, such
739 for the 32-bit class of object files.
740 An object may have multiple
743 This section holds a symbol hash table.
744 All object participating in
745 dynamic linking must contain a symbol hash table.
747 have only one hash table.
749 This section holds information for dynamic linking.
751 have only one dynamic section.
753 This section holds information that marks the file in some way.
755 A section of this type occupies no space in the file but otherwise
758 Although this section contains no bytes, the
760 member contains the conceptual file offset.
762 This section holds relocation offsets without explicit addends, such
765 for the 32-bit class of object files.
766 An object file may have multiple
769 This section is reserved but has unspecified semantics.
771 This section holds a minimal set of dynamic linking symbols.
773 object file can also contain a
777 This value up to and including
779 are reserved for processor-specific semantics.
781 This value down to and including
783 are reserved for processor-specific semantics.
785 This value specifies the lower bound of the range of indices reserved for
786 application programs.
788 This value specifies the upper bound of the range of indices reserved for
789 application programs.
790 Section types between
794 may be used by the application, without conflicting with current or future
795 system-defined section types.
799 Sections support one-bit flags that describe miscellaneous attributes.
800 If a flag bit is set in
805 Otherwise, the attribute is
808 Undefined attributes are set to zero.
810 .Bl -tag -width ".Dv SHF_EXECINSTR" -compact
812 This section contains data that should be writable during process
815 The section occupies memory during process execution.
817 sections do not reside in the memory image of an object file.
819 attribute is off for those sections.
821 The section contains executable machine instructions.
823 All bits included in this mask are reserved for processor-specific
828 If the section will appear in the memory image of a process, this member
829 holds the address at which the section's first byte should reside.
830 Otherwise, the member contains zero.
832 This member's value holds the byte offset from the beginning of the file
833 to the first byte in the section.
836 occupies no space in the file, and its
838 member locates the conceptual placement in the file.
840 This member holds the section's size in bytes.
841 Unless the section type
849 may have a non-zero size, but it occupies no space in the file.
851 This member holds a section header table index link, whose interpretation
852 depends on the section type.
854 This member holds extra information, whose interpretation depends on the
857 Some sections have address alignment constraints.
859 doubleword, the system must ensure doubleword alignment for the entire
861 That is, the value of
863 must be congruent to zero, modulo the value of
865 Only zero and positive integral powers of two are allowed.
867 or one mean the section has no alignment constraints.
869 Some sections hold a table of fixed-sized entries, such as a symbol table.
870 For such a section, this member gives the size in bytes for each entry.
871 This member contains zero if the section does not hold a table of
875 Various sections hold program and control information:
876 .Bl -tag -width ".Sy .shstrtab" -compact
878 (Block Started by Symbol)
879 This section holds uninitialized data that contributes to the program's
881 By definition, the system initializes the data with zeros
882 when the program begins to run.
883 This section is of type
885 The attributes types are
890 This section holds version control information.
891 This section is of type
893 No attribute types are used.
895 This section holds initialized data that contribute to the program's
897 This section is of type
899 The attribute types are
904 This section holds initialized data that contribute to the program's
906 This section is of type
908 The attribute types are
913 This section holds information for symbolic debugging.
916 This section is of type
918 No attribute types are used.
920 This section holds dynamic linking information.
921 The section's attributes
927 bit is set is processor-specific.
928 This section is of type
930 See the attributes above.
932 This section holds strings needed for dynamic linking, most commonly
933 the strings that represent the names associated with symbol table entries.
934 This section is of type
936 The attribute type used is
939 This section holds the dynamic linking symbol table.
940 This section is of type
942 The attribute used is
945 This section holds executable instructions that contribute to the process
947 When a program exits normally the system arranges to
948 execute the code in this section.
949 This section is of type
951 The attributes used are
956 This section holds the global offset table.
957 This section is of type
959 The attributes are processor-specific.
961 This section holds a symbol hash table.
962 This section is of type
964 The attribute used is
967 This section holds executable instructions that contribute to the process
969 When a program starts to run the system arranges to
970 execute the code in this section before calling the main program entry point.
971 This section is of type
973 The attributes used are
978 This section holds the pathname of a program interpreter.
980 a loadable segment that includes the section, the section's attributes will
984 Otherwise, that bit will be off.
985 This section is of type
988 This section holds line number information for symbolic debugging, which
989 describes the correspondence between the program source and the machine code.
990 The contents are unspecified.
991 This section is of type
993 No attribute types are used.
995 This section holds information in the
997 format described below.
998 This section is of type
1000 No attribute types are used.
1002 This section holds the procedure linkage table.
1003 This section is of type
1005 The attributes are processor-specific.
1007 This section holds relocation information as described below.
1009 has a loadable segment that includes relocation, the section's attributes
1013 Otherwise the bit will be off.
1016 is supplied by the section to which the relocations apply.
1020 normally would have the name
1022 This section is of type
1025 This section holds relocation information as described below.
1027 has a loadable segment that includes relocation, the section's attributes
1031 Otherwise the bit will be off.
1034 is supplied by the section to which the relocations apply.
1038 normally would have the name
1040 This section is of type
1043 This section holds read-only data that typically contributes to a
1044 non-writable segment in the process image.
1045 This section is of type
1047 The attribute used is
1050 This section hold read-only data that typically contributes to a
1051 non-writable segment in the process image.
1052 This section is of type
1054 The attribute used is
1057 This section holds section names.
1058 This section is of type
1060 No attribute types are used.
1062 This section holds strings, most commonly the strings that represent the
1063 names associated with symbol table entries.
1064 If the file has a loadable
1065 segment that includes the symbol string table, the section's attributes
1069 Otherwise the bit will be off.
1070 This section is of type
1073 This section holds a symbol table.
1074 If the file has a loadable segment
1075 that includes the symbol table, the section's attributes will include
1079 Otherwise the bit will be off.
1080 This section is of type
1083 This section holds the
1085 or executable instructions, of a program.
1086 This section is of type
1088 The attributes used are
1094 String table sections hold null-terminated character sequences, commonly
1096 The object file uses these strings to represent symbol
1098 One references a string as an index into the string
1100 The first byte, which is index zero, is defined to hold
1102 Similarly, a string table's last byte is defined to
1103 hold a null character, ensuring null termination for all strings.
1105 An object file's symbol table holds information needed to locate and
1106 relocate a program's symbolic definitions and references.
1108 index is a subscript into this array.
1109 .Bd -literal -offset indent
1112 Elf32_Addr st_value;
1114 unsigned char st_info;
1115 unsigned char st_other;
1116 Elf32_Half st_shndx;
1119 .Bd -literal -offset indent
1122 unsigned char st_info;
1123 unsigned char st_other;
1124 Elf64_Quarter st_shndx;
1125 Elf64_Addr st_value;
1130 .Bl -tag -width ".Fa st_value" -compact
1132 This member holds an index into the object file's symbol string table,
1133 which holds character representations of the symbol names.
1135 is non-zero, it represents a string table index that gives the symbol
1137 Otherwise, the symbol table has no name.
1139 This member gives the value of the associated symbol.
1141 Many symbols have associated sizes.
1142 This member holds zero if the symbol
1143 has no size or an unknown size.
1145 This member specifies the symbol's type and binding attributes:
1147 .Bl -tag -width ".Dv STT_SECTION" -compact
1149 The symbol's type is not defined.
1151 The symbol is associated with a data object.
1153 The symbol is associated with a function or other executable code.
1155 The symbol is associated with a section.
1156 Symbol table entries of
1157 this type exist primarily for relocation and normally have
1161 By convention the symbol's name gives the name of the source file
1162 associated with the object file.
1165 bindings, its section index is
1167 and it precedes the other
1169 symbols of the file, if it is present.
1171 This value up to and including
1173 are reserved for processor-specific semantics.
1175 This value down to and including
1177 are reserved for processor-specific semantics.
1180 .Bl -tag -width ".Dv STB_GLOBAL" -compact
1182 Local symbols are not visible outside the object file containing their
1184 Local symbols of the same name may exist in multiple file
1185 without interfering with each other.
1187 Global symbols are visible to all object files being combined.
1189 definition of a global symbol will satisfy another file's undefined
1190 reference to the same symbol.
1192 Weak symbols resemble global symbols, but their definitions have lower
1195 This value up to and including
1197 are reserved for processor-specific semantics.
1199 This value down to and including
1201 are reserved for processor-specific semantics.
1203 There are macros for packing and unpacking the binding and type fields:
1205 .Bl -tag -width ".Fn ELF32_ST_INFO bind type" -compact
1207 .Fn ELF32_ST_BIND info
1210 .Fn ELF64_ST_BIND info
1211 extract a binding from an
1215 .Fn ELF64_ST_TYPE info
1218 .Fn ELF32_ST_TYPE info
1219 extract a type from an
1223 .Fn ELF32_ST_INFO bind type
1226 .Fn ELF64_ST_INFO bind type
1227 convert a binding and a type into an
1234 This member currently holds zero and has no defined meaning.
1236 Every symbol table entry is
1238 in relation to some section.
1239 This member holds the relevant section
1243 Relocation is the process of connecting symbolic references with
1244 symbolic definitions.
1245 Relocatable files must have information that
1246 describes how to modify their section contents, thus allowing executable
1247 and shared object files to hold the right information for a process'
1249 Relocation entries are these data.
1251 Relocation structures that do not need an addend:
1252 .Bd -literal -offset indent
1254 Elf32_Addr r_offset;
1258 .Bd -literal -offset indent
1260 Elf64_Addr r_offset;
1265 Relocation structures that need an addend:
1266 .Bd -literal -offset indent
1268 Elf32_Addr r_offset;
1270 Elf32_Sword r_addend;
1273 .Bd -literal -offset indent
1275 Elf64_Addr r_offset;
1281 .Bl -tag -width ".Fa r_offset" -compact
1283 This member gives the location at which to apply the relocation action.
1284 For a relocatable file, the value is the byte offset from the beginning
1285 of the section to the storage unit affected by the relocation.
1287 executable file or shared object, the value is the virtual address of
1288 the storage unit affected by the relocation.
1290 This member gives both the symbol table index with respect to which the
1291 relocation must be made and the type of relocation to apply.
1293 types are processor-specific.
1294 When the text refers to a relocation
1295 entry's relocation type or symbol table index, it means the result of
1297 .Fn ELF[32|64]_R_TYPE
1299 .Fn ELF[32|64]_R_SYM ,
1300 respectively to the entry's
1304 This member specifies a constant addend used to compute the value to be
1305 stored into the relocatable field.
1317 .%B Elf-64 Object File Format
1320 .%A Santa Cruz Operation
1321 .%B System V Application Binary Interface
1324 .%A Unix System Laboratories
1326 .%B "Executable and Linking Format (ELF)"
1329 The ELF header files made their appearance in
1331 ELF in itself first appeared in
1333 The ELF format is an adopted standard.
1335 This manual page was written by
1336 .An Jeroen Ruigrok van der Werven
1337 .Aq asmodai@FreeBSD.org
1338 with inspiration from BSDi's