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 $
32 .Nd format of ELF executable binary files
38 defines the format of ELF executable binary files.
39 Amongst these files are
40 normal executable files, relocatable object files, core files and shared
43 An executable file using the ELF file format consists of an ELF header,
44 followed by a program header table or a section header table, or both.
45 The ELF header is always at offset zero of the file.
47 table and the section header table's offset in the file are defined in the
49 The two tables describe the rest of the particularities of
52 Applications which wish to process ELF binary files for their native
53 architecture only should include
56 These applications should need to refer to
57 all the types and structures by their generic names
61 Applications written this way can be compiled on any architecture,
62 regardless whether the host is 32-bit or 64-bit.
64 Should an application need to process ELF files of an unknown
65 architecture then the application needs to include both
71 Furthermore, all types and structures need to be identified by either
75 The macros need to be identified by
80 Whatever the system's architecture is, it will always include
83 .Pa sys/elf_generic.h .
85 These header files describe the above mentioned headers as C structures
86 and also include structures for dynamic sections, relocation sections and
89 The following types are being used for 32-bit architectures:
90 .Bd -literal -offset indent
91 Elf32_Addr Unsigned program address
92 Elf32_Half Unsigned halfword field
93 Elf32_Off Unsigned file offset
94 Elf32_Sword Signed large integer
95 Elf32_Word Field or unsigned large integer
96 Elf32_Size Unsigned object size
99 For 64-bit architectures we have the following types:
100 .Bd -literal -offset indent
101 Elf64_Addr Unsigned program address
102 Elf64_Half Unsigned halfword field
103 Elf64_Off Unsigned file offset
104 Elf64_Sword Signed large integer
105 Elf64_Word Field or unsigned large integer
106 Elf64_Size Unsigned object size
107 Elf64_Quarter Unsigned quarterword field
110 All data structures that the file format defines follow the
112 size and alignment guidelines for the relevant class.
114 data structures contain explicit padding to ensure 4-byte alignment
115 for 4-byte objects, to force structure sizes to a multiple of 4, etc.
117 The ELF header is described by the type Elf32_Ehdr or Elf64_Ehdr:
118 .Bd -literal -offset indent
120 unsigned char e_ident[EI_NIDENT];
122 Elf32_Half e_machine;
123 Elf32_Word e_version;
129 Elf32_Half e_phentsize;
131 Elf32_Half e_shentsize;
133 Elf32_Half e_shstrndx;
137 .Bd -literal -offset indent
139 unsigned char e_ident[EI_NIDENT];
140 Elf64_Quarter e_type;
141 Elf64_Quarter e_machine;
142 Elf64_Half e_version;
147 Elf64_Quarter e_ehsize;
148 Elf64_Quarter e_phentsize;
149 Elf64_Quarter e_phnum;
150 Elf64_Quarter e_shentsize;
151 Elf64_Quarter e_shnum;
152 Elf64_Quarter e_shstrndx;
156 The fields have the following meanings:
158 .Bl -tag -width "e_phentsize" -compact -offset indent
160 This array of bytes specifies to interpret the file,
161 independent of the processor or the file's remaining contents.
162 Within this array everything is named by macros, which start with
165 and may contain values which start with the prefix
167 The following macros are defined:
169 .Bl -tag -width "EI_ABIVERSION" -compact
171 The first byte of the magic number.
172 It must be filled with
175 The second byte of the magic number.
176 It must be filled with
179 The third byte of the magic number.
180 It must be filled with
183 The fourth byte of the magic number.
184 It must be filled with
187 The fifth byte identifies the architecture for this binary:
189 .Bl -tag -width "ELFCLASSNONE" -compact
191 This class is invalid.
193 This defines the 32-bit architecture.
194 It supports machines with files
195 and virtual address spaces up to 4 Gigabytes.
197 This defines the 64-bit architecture.
200 The sixth byte specifies the data encoding of the processor-specific
202 Currently these encodings are supported:
204 .Bl -tag -width "ELFDATA2LSB" -compact
208 Two's complement, little-endian.
210 Two's complement, big-endian.
213 The version number of the ELF specification:
215 .Bl -tag -width "EV_CURRENT" -compact
222 This byte identifies the operating system
223 and ABI to which the object is targeted.
224 Some fields in other ELF structures have flags
225 and values that have platform specific meanings;
226 the interpretation of those fields is determined by the value of this byte.
227 The following values are currently defined:
229 .Bl -tag -width "ELFOSABI_STANDALONE" -compact
233 HP-UX operating system ABI.
234 .It Dv ELFOSABI_NETBSD
236 operating system ABI.
237 .It Dv ELFOSABI_LINUX
238 GNU/Linux operating system ABI.
240 GNU/Hurd operating system ABI.
241 .It Dv ELFOSABI_86OPEN
242 86Open Common IA32 ABI.
243 .It Dv ELFOSABI_SOLARIS
244 Solaris operating system ABI.
245 .It Dv ELFOSABI_MONTEREY
246 Monterey project ABI.
248 IRIX operating system ABI.
249 .It Dv ELFOSABI_FREEBSD
251 operating system ABI.
252 .It Dv ELFOSABI_TRU64
253 TRU64 UNIX operating system ABI.
255 ARM architecture ABI.
256 .It Dv ELFOSABI_STANDALONE
257 Standalone (embedded) ABI.
260 This byte identifies the version of the ABI
261 to which the object is targeted.
262 This field is used to distinguish among incompatible versions of an ABI.
263 The interpretation of this version number
264 is dependent on the ABI identified by the EI_OSABI field.
265 Applications conforming to this specification use the value 0.
268 These bytes are reserved and set to zero.
270 which read them should ignore them.
271 The value for EI_PAD will change in
272 the future if currently unused bytes are given meanings.
274 Start of architecture identification.
276 The size of the e_ident array.
280 This member of the structure identifies the object file type:
282 .Bl -tag -width "ET_NONE" -compact
296 This member specifies the required architecture for an individual file:
298 .Bl -tag -width "EM_MIPS_RS4_BE" -compact
304 Sun Microsystems SPARC.
316 MIPS RS3000 (big-endian only).
317 .It Dv EM_MIPS_RS4_BE
318 MIPS RS4000 (big-endian only).
320 SPARC v9 64-bit unofficial.
330 This member identifies the file version:
332 .Bl -tag -width "EV_CURRENT" -compact
339 This member gives the virtual address to which the system first transfers
340 control, thus starting the process.
341 If the file has no associated entry
342 point, this member holds zero.
344 This member holds the program header table's file offset in bytes.
346 the file has no program header table, this member holds zero.
348 This member holds the section header table's file offset in bytes.
350 file has no section header table this member holds zero.
352 This member holds processor-specific flags associated with the file.
354 names take the form EF_`machine_flag'. Currently no flags have been defined.
356 This member holds the ELF header's size in bytes.
358 This member holds the size in bytes of one entry in the file's program header
359 table; all entries are the same size.
361 This member holds the number of entries in the program header
367 gives the table's size
369 If a file has no program header,
371 holds the value zero.
373 This member holds a sections header's size in bytes.
374 A section header is one
375 entry in the section header table; all entries are the same size.
377 This member holds the number of entries in the section header table.
383 gives the section header table's size in bytes.
384 If a file has no section
387 holds the value of zero.
389 This member holds the section header table index of the entry associated
390 with the section name string table.
391 If the file has no section name string
392 table, this member holds the value
395 .Bl -tag -width "SHN_LORESERVE" -compact
397 This value marks an undefined, missing, irrelevant, or otherwise meaningless
399 For example, a symbol
401 relative to section number
403 is an undefined symbol.
405 This value specifies the lower bound of the range of reserved indexes.
407 This value up to and including
409 are reserved for processor-specific semantics.
411 This value down to and including
413 are reserved for processor-specific semantics.
415 This value specifies absolute values for the corresponding reference.
417 example, symbols defined relative to section number
419 have absolute values and are not affected by relocation.
421 Symbols defined relative to this section are common symbols, such as Fortran
422 COMMON or unallocated C external variables.
424 This value specifies the upper bound of the range of the range of reserved
429 inclusive; the values do
430 not reference the section header table.
431 That is, the section header table
434 contain entries for the reserved indices.
438 An executable or shared object file's program header table is an array of
439 structures, each describing a segment or other information the system needs
440 to prepare the program for execution.
445 Program headers are meaningful only for executable and shared object files.
446 A file specifies its own program header size with the ELF header's
451 As with the Elf executable header, the program header
452 also has different versions depending on the architecture:
454 .Bd -literal -offset indent
467 .Bd -literal -offset indent
480 The main difference between the 32-bit and the 64-bit program header lies
481 only in the location of a
483 member in the total struct.
485 .Bl -tag -width "p_offset" -compact -offset indent
487 This member of the Phdr struct tells what kind of segment this array
488 element describes or how to interpret the array element's information.
489 .Bl -tag -width "PT_DYNAMIC" -compact
492 The array element is unused and the other members' values are undefined.
493 This lets the program header have ignored entries.
495 The array element specifies a loadable segment, described by
499 The bytes from the file are mapped to the beginning of the memory
501 If the segment's memory size
503 is larger than the file size
507 bytes are defined to hold the value 0 and to follow the segment's
509 The file size may not be larger than the memory size.
510 Loadable segment entries in the program header table appear in ascending
515 The array element specifies dynamic linking information.
517 The array element specifies the location and size of a null-terminated
518 path name to invoke as an interpreter.
519 This segment type is meaningful
520 only for executable files (though it may occur for shared objects). However
521 it may not occur more than once in a file.
522 If it is present it must precede
523 any loadable segment entry.
525 The array element specifies the location and size for auxiliary information.
527 This segment type is reserved but has unspecified semantics.
529 contain an array element of this type do not conform to the ABI.
531 The array element, if present, specifies the location and size of the program
532 header table itself, both in the file and in the memory image of the program.
533 This segment type may not occur more than once in a file.
535 only occur if the program header table is part of the memory image of the
537 If it is present it must precede any loadable segment entry.
539 This value up to and including
541 are reserved for processor-specific semantics.
543 This value down to and including
545 are reserved for processor-specific semantics.
549 This member holds the offset from the beginning of the file at which
550 the first byte of the of the segment resides.
552 This member holds the virtual address at which the first byte of the
553 segment resides in memory.
555 On systems for which physical addressing is relevant, this member is
556 reserved for the segment's physical address.
560 not used and must be zero.
562 This member holds the number of bytes in the file image of the segment.
565 This member holds the number of bytes in the memory image of the segment.
568 This member holds flags relevant to the segment:
570 .Bl -tag -width "PF_X" -compact
572 An executable segment.
579 A text segment commonly has the flags
583 A data segment commonly has
589 This member holds the value to which the segments are aligned in memory
591 Loadable process segments must have congruent values for
595 modulo the page size.
596 Values of zero and one mean no alignment is required.
599 should be a positive, integral power of two, and
607 An file's section header table lets one locate all the file's sections.
609 section header table is an array of Elf32_Shdr or Elf64_Shdr structures.
613 member gives the byte offset from the beginning of the file to the section
616 holds the number of entries the section header table contains.
618 holds the size in bytes of each entry.
620 A section header table index is a subscript into this array.
622 header table indices are reserved.
623 An object file does not have sections for
624 these special indices:
626 .Bl -tag -width "SHN_LORESERVE" -compact
628 This value marks an undefined, missing, irrelevant or otherwise meaningless
631 This value specifies the lower bound of the range of reserved indices.
633 This value up to and including
635 are reserved for processor-specific semantics.
637 This value down to and including
639 are reserved for processor-specific semantics.
641 This value specifies absolute values for the corresponding reference.
643 example, symbols defined relative to section number
645 have absolute values and are not affected by relocation.
647 Symbols defined relative to this section are common symbols, such as FORTRAN
648 COMMON or unallocated C external variables.
650 This value specifies the upper bound of the range of reserved indices.
652 system reserves indices between
657 The section header table does not contain entries for the
661 The section header has the following structure:
662 .Bd -literal -offset indent
672 Elf32_Size sh_addralign;
673 Elf32_Size sh_entsize;
677 .Bd -literal -offset indent
687 Elf64_Size sh_addralign;
688 Elf64_Size sh_entsize;
692 .Bl -tag -width "sh_addralign" -compact
694 This member specifies the name of the section.
695 Its value is an index
696 into the section header string table section, giving the location of
697 a null-terminated string.
699 This member categorizes the section's contents and semantics.
701 .Bl -tag -width "SHT_PROGBITS" -compact
703 This value marks the section header as inactive.
705 have an associated section.
706 Other members of the section header
707 have undefined values.
709 The section holds information defined by the program, whose
710 format and meaning are determined solely by the program.
712 This section holds a symbol table.
715 provides symbols for link editing, though it may also be used
717 As a complete symbol table, it may contain
718 many symbols unnecessary for dynamic linking.
724 This section holds a string table.
725 An object file may have multiple
726 string table sections.
728 This section holds relocation entries with explicit addends, such
731 for the 32-bit class of object files.
732 An object may have multiple
735 This section holds a symbol hash table.
736 All object participating in
737 dynamic linking must contain a symbol hash table.
739 have only one hash table.
741 This section holds information for dynamic linking.
743 have only one dynamic section.
745 This section holds information that marks the file in some way.
747 A section of this type occupies no space in the file but otherwise
750 Although this section contains no bytes, the
752 member contains the conceptual file offset.
754 This section holds relocation offsets without explicit addends, such
757 for the 32-bit class of object files.
758 An object file may have multiple
761 This section is reserved but has unspecified semantics.
763 This section holds a minimal set of dynamic linking symbols.
765 object file can also contain a
769 This value up to and including
771 are reserved for processor-specific semantics.
773 This value down to and including
775 are reserved for processor-specific semantics.
777 This value specifies the lower bound of the range of indices reserved for
778 application programs.
780 This value specifies the upper bound of the range of indices reserved for
781 application programs.
782 Section types between
786 may be used by the application, without conflicting with current or future
787 system-defined section types.
791 Sections support one-bit flags that describe miscellaneous attributes.
792 If a flag bit is set in
797 Otherwise, the attribute is
800 Undefined attributes are set to zero.
802 .Bl -tag -width "SHF_EXECINSTR" -compact
804 This section contains data that should be writable during process
807 The section occupies memory during process execution.
809 sections do not reside in the memory image of an object file.
811 attribute is off for those sections.
813 The section contains executable machine instructions.
815 All bits included in this mask are reserved for processor-specific
820 If the section will appear in the memory image of a process, this member
821 holds the address at which the section's first byte should reside.
822 Otherwise, the member contains zero.
824 This member's value holds the byte offset from the beginning of the file
825 to the first byte in the section.
828 occupies no space in the file, and its
830 member locates the conceptual placement in the file.
832 This member holds the section's size in bytes.
833 Unless the section type
841 may have a non-zero size, but it occupies no space in the file.
843 This member holds a section header table index link, whose interpretation
844 depends on the section type.
846 This member holds extra information, whose interpretation depends on the
849 Some sections have address alignment constraints.
851 doubleword, the system must ensure doubleword alignment for the entire
853 That is, the value of
855 must be congruent to zero, modulo the value of
857 Only zero and positive integral powers of two are allowed.
859 or one mean the section has no alignment constraints.
861 Some sections hold a table of fixed-sized entries, such as a symbol table.
862 For such a section, this member gives the size in bytes for each entry.
863 This member contains zero if the section does not hold a table of
867 Various sections hold program and control information:
868 .Bl -tag -width ".shstrtab" -compact
870 This section holds uninitialized data that contributes to the program's
872 By definition, the system initializes the data with zeros
873 when the program begins to run.
874 This section is of type
876 The attributes types are
881 This section holds version control information.
882 This section is of type
884 No attribute types are used.
886 This section holds initialized data that contribute to the program's
888 This section is of type
890 The attribute types are
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 information for symbolic debugging.
907 This section is of type
909 No attribute types are used.
911 This section holds dynamic linking information.
912 The section's attributes
918 bit is set is processor-specific.
919 This section is of type
921 See the attributes above.
923 This section holds strings needed for dynamic linking, most commonly
924 the strings that represent the names associated with symbol table entries.
925 This section is of type
927 The attribute type used is
930 This section holds the dynamic linking symbol table.
931 This section is of type
933 The attribute used is
936 This section holds executable instructions that contribute to the process
938 When a program exits normally the system arranges to
939 execute the code in this section.
940 This section is of type
942 The attributes used are
947 This section holds the global offset table.
948 This section is of type
950 The attributes are processor-specific.
952 This section holds a symbol hash table.
953 This section is of type
955 The attribute used is
958 This section holds executable instructions that contribute to the process
960 When a program starts to run the system arranges to
961 execute the code in this section before calling the main program entry point.
962 This section is of type
964 The attributes used are
969 This section holds the pathname of a program interpreter.
971 a loadable segment that includes the section, the section's attributes will
975 Otherwise, that bit will be off.
976 This section is of type
979 This section holds line number information for symbolic debugging, which
980 describes the correspondence between the program source and the machine code.
981 The contents are unspecified.
982 This section is of type
984 No attribute types are used.
986 This section holds information in the
988 format described below.
989 This section is of type
991 No attribute types are used.
993 This section holds the procedure linkage table.
994 This section is of type
996 The attributes are processor-specific.
998 This section holds relocation information as described below.
1000 has a loadable segment that includes relocation, the section's attributes
1004 Otherwise the bit will be off.
1007 is supplied by the section to which the relocations apply.
1011 normally would have the name
1013 This section is of type
1016 This section holds relocation information as described below.
1018 has a loadable segment that includes relocation, the section's attributes
1022 Otherwise the bit will be off.
1025 is supplied by the section to which the relocations apply.
1029 normally would have the name
1031 This section is of type
1034 This section holds read-only data that typically contributes to a
1035 non-writable segment in the process image.
1036 This section is of type
1038 The attribute used is
1041 This section hold read-only data that typically contributes to a
1042 non-writable segment in the process image.
1043 This section is of type
1045 The attribute used is
1048 This section holds section names.
1049 This section is of type
1051 No attribute types are used.
1053 This section holds strings, most commonly the strings that represent the
1054 names associated with symbol table entries.
1055 If the file has a loadable
1056 segment that includes the symbol string table, the section's attributes
1060 Otherwise the bit will be off.
1061 This section is of type
1064 This section holds a symbol table.
1065 If the file has a loadable segment
1066 that includes the symbol table, the section's attributes will include
1070 Otherwise the bit will be off.
1071 This section is of type
1074 This section holds the
1076 or executable instructions, of a program.
1077 This section is of type
1079 The attributes used are
1085 String table sections hold null-terminated character sequences, commonly
1087 The object file uses these strings to represent symbol
1089 One references a string as an index into the string
1091 The first byte, which is index zero, is defined to hold
1093 Similarly, a string table's last byte is defined to
1094 hold a null character, ensuring null termination for all strings.
1096 An object file's symbol table holds information needed to locate and
1097 relocate a program's symbolic definitions and references.
1099 index is a subscript into this array.
1101 .Bd -literal -offset indent
1104 Elf32_Addr st_value;
1106 unsigned char st_info;
1107 unsigned char st_other;
1108 Elf32_Half st_shndx;
1112 .Bd -literal -offset indent
1115 unsigned char st_info;
1116 unsigned char st_other;
1117 Elf64_Quarter st_shndx;
1118 Elf64_Addr st_value;
1123 .Bl -tag -width "st_value" -compact
1125 This member holds an index into the object file's symbol string table,
1126 which holds character representations of the symbol names.
1128 is non-zero, it represents a string table index that gives the symbol
1130 Otherwise, the symbol table has no name.
1132 This member gives the value of the associated symbol.
1134 Many symbols have associated sizes.
1135 This member holds zero if the symbol
1136 has no size or an unknown size.
1138 This member specifies the symbol's type and binding attributes:
1140 .Bl -tag -width "STT_SECTION" -compact
1142 The symbol's type is not defined.
1144 The symbol is associated with a data object.
1146 The symbol is associated with a function or other executable code.
1148 The symbol is associated with a section.
1149 Symbol table entries of
1150 this type exist primarily for relocation and normally have
1154 By convention the symbol's name gives the name of the source file
1155 associated with the object file.
1158 bindings, its section index is
1160 and it precedes the other
1162 symbols of the file, if it is present.
1164 This value up to and including
1166 are reserved for processor-specific semantics.
1168 This value down to and including
1170 are reserved for processor-specific semantics.
1173 .Bl -tag -width "STB_GLOBAL" -compact
1175 Local symbols are not visible outside the object file containing their
1177 Local symbols of the same name may exist in multiple file
1178 without interfering with each other.
1180 Global symbols are visible to all object files being combined.
1182 definition of a global symbol will satisfy another file's undefined
1183 reference to the same symbol.
1185 Weak symbols resemble global symbols, but their definitions have lower
1188 This value up to and including
1190 are reserved for processor-specific semantics.
1192 This value down to and including
1194 are reserved for processor-specific semantics.
1196 There are macros for packing and unpacking the binding and type fields:
1198 .Bl -tag -width "ELF32_ST_INFO(bind, type)" -compact
1200 .Fn ELF32_ST_BIND info
1203 .Fn ELF64_ST_BIND info
1204 extract a binding from an st_info value.
1206 .Fn ELF64_ST_TYPE info
1209 .Fn ELF32_ST_TYPE info
1210 extract a type from an st_info value.
1212 .Fn ELF32_ST_INFO bind type
1215 .Fn ELF64_ST_INFO bind type
1216 convert a binding and a type into an st_info value.
1221 This member currently holds zero and has no defined meaning.
1223 Every symbol table entry is
1225 in relation to some action.
1226 This member holds the relevant section
1230 Relocation is the process of connecting symbolic references with
1231 symbolic definitions.
1232 Relocatable files must have information that
1233 describes how to modify their section contents, thus allowing executable
1234 and shared object files to hold the right information for a process'
1236 Relocation entries are these data.
1238 Relocation structures that do not need an addend:
1240 .Bd -literal -offset indent
1242 Elf32_Addr r_offset;
1246 .Bd -literal -offset indent
1248 Elf64_Addr r_offset;
1253 Relocation structures that need an addend:
1255 .Bd -literal -offset indent
1257 Elf32_Addr r_offset;
1259 Elf32_Sword r_addend;
1262 .Bd -literal -offset indent
1264 Elf64_Addr r_offset;
1270 .Bl -tag -width "r_offset" -compact
1272 This member gives the location at which to apply the relocation action.
1273 For a relocatable file, the value is the byte offset from the beginning
1274 of the section to the storage unit affected by the relocation.
1276 executable file or shared object, the value is the virtual address of
1277 the storage unit affected by the relocation.
1279 This member gives both the symbol table index with respect to which the
1280 relocation must be made and the type of relocation to apply.
1282 types are processor-specific.
1283 When the text refers to a relocation
1284 entry's relocation type or symbol table index, it means the result of
1286 .Sy ELF_[32|64]_R_TYPE
1288 .Sy ELF[32|64]_R_SYM ,
1289 respectively to the entry's
1293 This member specifies a constant addend used to compute the value to be
1294 stored into the relocatable field.
1305 .%B Elf-64 Object File Format
1308 .%A Santa Cruz Operation
1309 .%B System V Application Binary Interface
1312 .%A Unix System Laboratories
1314 .%B "Executable and Linking Format (ELF)"
1317 The ELF header files made their appearance in
1319 ELF in itself first appeared in
1321 The ELF format is an adopted standard.
1323 This manual page was written by
1324 .An Jeroen Ruigrok van der Werven
1325 .Aq asmodai@FreeBSD.org
1326 with inspiration from BSDi's