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
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 .In 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 32-bit program address
92 Elf32_Half Unsigned 16-bit field
93 Elf32_Lword Unsigned 64-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
99 For 64-bit architectures we have the following types:
100 .Bd -literal -offset indent
101 Elf64_Addr Unsigned 64-bit program address
102 Elf64_Half Unsigned 16-bit field
103 Elf64_Lword Unsigned 64-bit field
104 Elf64_Off Unsigned 64-bit file offset
105 Elf64_Sword Signed 32-bit field
106 Elf64_Sxword Signed 64-bit field or integer
107 Elf64_Word Unsigned 32-bit field
108 Elf64_Xword Unsigned 64-bit field or integer
111 All data structures that the file format defines follow the
113 size and alignment guidelines for the relevant class.
115 data structures contain explicit padding to ensure 4-byte alignment
116 for 4-byte objects, to force structure sizes to a multiple of 4, etc.
118 The ELF header is described by the type Elf32_Ehdr or Elf64_Ehdr:
119 .Bd -literal -offset indent
121 unsigned char e_ident[EI_NIDENT];
123 Elf32_Half e_machine;
124 Elf32_Word e_version;
130 Elf32_Half e_phentsize;
132 Elf32_Half e_shentsize;
134 Elf32_Half e_shstrndx;
138 .Bd -literal -offset indent
140 unsigned char e_ident[EI_NIDENT];
142 Elf64_Half e_machine;
143 Elf64_Word e_version;
149 Elf64_Half e_phentsize;
151 Elf64_Half e_shentsize;
153 Elf64_Half e_shstrndx;
157 The fields have the following meanings:
159 .Bl -tag -width "e_phentsize" -compact -offset indent
161 This array of bytes specifies to interpret the file,
162 independent of the processor or the file's remaining contents.
163 Within this array everything is named by macros, which start with
166 and may contain values which start with the prefix
168 The following macros are defined:
170 .Bl -tag -width "EI_ABIVERSION" -compact
172 The first byte of the magic number.
173 It must be filled with
176 The second byte of the magic number.
177 It must be filled with
180 The third byte of the magic number.
181 It must be filled with
184 The fourth byte of the magic number.
185 It must be filled with
188 The fifth byte identifies the architecture for this binary:
190 .Bl -tag -width "ELFCLASSNONE" -compact
192 This class is invalid.
194 This defines the 32-bit architecture.
195 It supports machines with files
196 and virtual address spaces up to 4 Gigabytes.
198 This defines the 64-bit architecture.
201 The sixth byte specifies the data encoding of the processor-specific
203 Currently these encodings are supported:
205 .Bl -tag -width "ELFDATA2LSB" -compact
209 Two's complement, little-endian.
211 Two's complement, big-endian.
214 The version number of the ELF specification:
216 .Bl -tag -width "EV_CURRENT" -compact
223 This byte identifies the operating system
224 and ABI to which the object is targeted.
225 Some fields in other ELF structures have flags
226 and values that have platform specific meanings;
227 the interpretation of those fields is determined by the value of this byte.
228 The following values are currently defined:
230 .Bl -tag -width "ELFOSABI_STANDALONE" -compact
234 HP-UX operating system ABI.
235 .It Dv ELFOSABI_NETBSD
237 operating system ABI.
238 .It Dv ELFOSABI_LINUX
239 GNU/Linux operating system ABI.
241 GNU/Hurd operating system ABI.
242 .It Dv ELFOSABI_86OPEN
243 86Open Common IA32 ABI.
244 .It Dv ELFOSABI_SOLARIS
245 Solaris operating system ABI.
246 .It Dv ELFOSABI_MONTEREY
247 Monterey project ABI.
249 IRIX operating system ABI.
250 .It Dv ELFOSABI_FREEBSD
252 operating system ABI.
253 .It Dv ELFOSABI_TRU64
254 TRU64 UNIX operating system ABI.
256 ARM architecture ABI.
257 .It Dv ELFOSABI_STANDALONE
258 Standalone (embedded) ABI.
261 This byte identifies the version of the ABI
262 to which the object is targeted.
263 This field is used to distinguish among incompatible versions of an ABI.
264 The interpretation of this version number
265 is dependent on the ABI identified by the EI_OSABI field.
266 Applications conforming to this specification use the value 0.
269 These bytes are reserved and set to zero.
271 which read them should ignore them.
272 The value for EI_PAD will change in
273 the future if currently unused bytes are given meanings.
275 Start of architecture identification.
277 The size of the e_ident array.
281 This member of the structure identifies the object file type:
283 .Bl -tag -width "ET_NONE" -compact
297 This member specifies the required architecture for an individual file:
299 .Bl -tag -width "EM_MIPS_RS4_BE" -compact
305 Sun Microsystems SPARC.
317 MIPS RS3000 (big-endian only).
318 .It Dv EM_MIPS_RS4_BE
319 MIPS RS4000 (big-endian only).
321 SPARC v9 64-bit unofficial.
331 This member identifies the file version:
333 .Bl -tag -width "EV_CURRENT" -compact
340 This member gives the virtual address to which the system first transfers
341 control, thus starting the process.
342 If the file has no associated entry
343 point, this member holds zero.
345 This member holds the program header table's file offset in bytes.
347 the file has no program header table, this member holds zero.
349 This member holds the section header table's file offset in bytes.
351 file has no section header table this member holds zero.
353 This member holds processor-specific flags associated with the file.
355 names take the form EF_`machine_flag'.
356 Currently no flags have been defined.
358 This member holds the ELF header's size in bytes.
360 This member holds the size in bytes of one entry in the file's program header
361 table; all entries are the same size.
363 This member holds the number of entries in the program header
365 If the file is using extended program header numbering, then the
367 member will contain the value
369 and the actual number of program header table entries will be stored
372 member of the section header at index
376 and the number of program header table entries gives the program
377 header table's size in bytes.
378 If a file has no program header,
380 holds the value zero.
382 This member holds a sections header's size in bytes.
383 A section header is one
384 entry in the section header table; all entries are the same size.
386 This member holds the number of entries in the section header table.
387 If the file is using extended section numbering, then the
389 member will be zero and the actual section number will be stored in the
391 member of the section header at index
393 If a file has no section header table, both the
397 fields of the ELF header will be zero.
400 and the number of sections in the file gives the section header
401 table's size in bytes.
403 This member holds the section header table index of the entry associated
404 with the section name string table.
405 If extended section numbering is being used, this field will hold the
408 and the actual section header table index will be present in the
410 field of the section header entry at index
412 If the file has no section name string
413 table, this member holds the value
417 An executable or shared object file's program header table is an array of
418 structures, each describing a segment or other information the system needs
419 to prepare the program for execution.
424 Program headers are meaningful only for executable and shared object files.
425 A file specifies its own program header size with the ELF header's
430 As with the Elf executable header, the program header
431 also has different versions depending on the architecture:
433 .Bd -literal -offset indent
446 .Bd -literal -offset indent
453 Elf64_Xword p_filesz;
459 The main difference between the 32-bit and the 64-bit program header lies
460 only in the location of a
462 member in the total struct.
464 .Bl -tag -width "p_offset" -compact -offset indent
466 This member of the Phdr struct tells what kind of segment this array
467 element describes or how to interpret the array element's information.
468 .Bl -tag -width "PT_DYNAMIC" -compact
471 The array element is unused and the other members' values are undefined.
472 This lets the program header have ignored entries.
474 The array element specifies a loadable segment, described by
478 The bytes from the file are mapped to the beginning of the memory
480 If the segment's memory size
482 is larger than the file size
486 bytes are defined to hold the value 0 and to follow the segment's
488 The file size may not be larger than the memory size.
489 Loadable segment entries in the program header table appear in ascending
494 The array element specifies dynamic linking information.
496 The array element specifies the location and size of a null-terminated
497 path name to invoke as an interpreter.
498 This segment type is meaningful
499 only for executable files (though it may occur for shared objects).
501 it may not occur more than once in a file.
502 If it is present it must precede
503 any loadable segment entry.
505 The array element specifies the location and size for auxiliary information.
507 This segment type is reserved but has unspecified semantics.
509 contain an array element of this type do not conform to the ABI.
511 The array element, if present, specifies the location and size of the program
512 header table itself, both in the file and in the memory image of the program.
513 This segment type may not occur more than once in a file.
515 only occur if the program header table is part of the memory image of the
517 If it is present it must precede any loadable segment entry.
519 This value up to and including
521 are reserved for processor-specific semantics.
523 This value down to and including
525 are reserved for processor-specific semantics.
529 This member holds the offset from the beginning of the file at which
530 the first byte of the segment resides.
532 This member holds the virtual address at which the first byte of the
533 segment resides in memory.
535 On systems for which physical addressing is relevant, this member is
536 reserved for the segment's physical address.
540 not used and must be zero.
542 This member holds the number of bytes in the file image of the segment.
545 This member holds the number of bytes in the memory image of the segment.
548 This member holds flags relevant to the segment:
550 .Bl -tag -width "PF_X" -compact
552 An executable segment.
559 A text segment commonly has the flags
563 A data segment commonly has
569 This member holds the value to which the segments are aligned in memory
571 Loadable process segments must have congruent values for
575 modulo the page size.
576 Values of zero and one mean no alignment is required.
579 should be a positive, integral power of two, and
587 An file's section header table lets one locate all the file's sections.
589 section header table is an array of Elf32_Shdr or Elf64_Shdr structures.
593 member gives the byte offset from the beginning of the file to the section
596 holds the number of entries the section header table contains.
598 holds the size in bytes of each entry.
600 A section header table index is a subscript into this array.
602 header table indices are reserved.
603 An object file does not have sections for
604 these special indices:
606 .Bl -tag -width "SHN_LORESERVE" -compact
608 This value marks an undefined, missing, irrelevant, or otherwise meaningless
610 For example, a symbol
612 relative to section number
614 is an undefined symbol.
616 This value specifies the lower bound of the range of reserved indices.
618 This value up to and including
620 are reserved for processor-specific semantics.
622 This value down to and including
624 are reserved for processor-specific semantics.
626 This value specifies absolute values for the corresponding reference.
628 example, symbols defined relative to section number
630 have absolute values and are not affected by relocation.
632 Symbols defined relative to this section are common symbols, such as FORTRAN
633 COMMON or unallocated C external variables.
635 This value specifies the upper bound of the range of reserved indices.
637 system reserves indices between
642 The section header table does not contain entries for the
646 The section header has the following structure:
647 .Bd -literal -offset indent
657 Elf32_Word sh_addralign;
658 Elf32_Word sh_entsize;
662 .Bd -literal -offset indent
666 Elf64_Xword sh_flags;
672 Elf64_Xword sh_addralign;
673 Elf64_Xword sh_entsize;
677 .Bl -tag -width "sh_addralign" -compact
679 This member specifies the name of the section.
680 Its value is an index
681 into the section header string table section, giving the location of
682 a null-terminated string.
684 This member categorizes the section's contents and semantics.
686 .Bl -tag -width "SHT_PROGBITS" -compact
688 This value marks the section header as inactive.
690 have an associated section.
691 Other members of the section header
692 have undefined values.
694 The section holds information defined by the program, whose
695 format and meaning are determined solely by the program.
697 This section holds a symbol table.
700 provides symbols for link editing, though it may also be used
702 As a complete symbol table, it may contain
703 many symbols unnecessary for dynamic linking.
709 This section holds a string table.
710 An object file may have multiple
711 string table sections.
713 This section holds relocation entries with explicit addends, such
716 for the 32-bit class of object files.
717 An object may have multiple
720 This section holds a symbol hash table.
721 All object participating in
722 dynamic linking must contain a symbol hash table.
724 have only one hash table.
726 This section holds information for dynamic linking.
728 have only one dynamic section.
730 This section holds information that marks the file in some way.
732 A section of this type occupies no space in the file but otherwise
735 Although this section contains no bytes, the
737 member contains the conceptual file offset.
739 This section holds relocation offsets without explicit addends, such
742 for the 32-bit class of object files.
743 An object file may have multiple
746 This section is reserved but has unspecified semantics.
748 This section holds a minimal set of dynamic linking symbols.
750 object file can also contain a
754 This value up to and including
756 are reserved for processor-specific semantics.
758 This value down to and including
760 are reserved for processor-specific semantics.
762 This value specifies the lower bound of the range of indices reserved for
763 application programs.
765 This value specifies the upper bound of the range of indices reserved for
766 application programs.
767 Section types between
771 may be used by the application, without conflicting with current or future
772 system-defined section types.
776 Sections support one-bit flags that describe miscellaneous attributes.
777 If a flag bit is set in
782 Otherwise, the attribute is
785 Undefined attributes are set to zero.
787 .Bl -tag -width "SHF_EXECINSTR" -compact
789 This section contains data that should be writable during process
792 The section occupies memory during process execution.
794 sections do not reside in the memory image of an object file.
796 attribute is off for those sections.
798 The section contains executable machine instructions.
800 All bits included in this mask are reserved for processor-specific
805 If the section will appear in the memory image of a process, this member
806 holds the address at which the section's first byte should reside.
807 Otherwise, the member contains zero.
809 This member's value holds the byte offset from the beginning of the file
810 to the first byte in the section.
813 occupies no space in the file, and its
815 member locates the conceptual placement in the file.
817 This member holds the section's size in bytes.
818 Unless the section type
826 may have a non-zero size, but it occupies no space in the file.
828 This member holds a section header table index link, whose interpretation
829 depends on the section type.
831 This member holds extra information, whose interpretation depends on the
834 Some sections have address alignment constraints.
836 doubleword, the system must ensure doubleword alignment for the entire
838 That is, the value of
840 must be congruent to zero, modulo the value of
842 Only zero and positive integral powers of two are allowed.
844 or one mean the section has no alignment constraints.
846 Some sections hold a table of fixed-sized entries, such as a symbol table.
847 For such a section, this member gives the size in bytes for each entry.
848 This member contains zero if the section does not hold a table of
852 Various sections hold program and control information:
853 .Bl -tag -width ".shstrtab" -compact
855 (Block Started by Symbol)
856 This section holds uninitialized data that contributes to the program's
858 By definition, the system initializes the data with zeros
859 when the program begins to run.
860 This section is of type
862 The attributes types are
867 This section holds version control information.
868 This section is of type
870 No attribute types are used.
872 This section holds initialized data that contribute to the program's
874 This section is of type
876 The attribute types are
881 This section holds initialized data that contribute to the program's
883 This section is of type
885 The attribute types are
890 This section holds information for symbolic debugging.
893 This section is of type
895 No attribute types are used.
897 This section holds dynamic linking information.
898 The section's attributes
904 bit is set is processor-specific.
905 This section is of type
907 See the attributes above.
909 This section holds strings needed for dynamic linking, most commonly
910 the strings that represent the names associated with symbol table entries.
911 This section is of type
913 The attribute type used is
916 This section holds the dynamic linking symbol table.
917 This section is of type
919 The attribute used is
922 This section holds executable instructions that contribute to the process
924 When a program exits normally the system arranges to
925 execute the code in this section.
926 This section is of type
928 The attributes used are
933 This section holds the global offset table.
934 This section is of type
936 The attributes are processor-specific.
938 This section holds a symbol hash 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 starts to run the system arranges to
947 execute the code in this section before calling the main program entry point.
948 This section is of type
950 The attributes used are
955 This section holds the pathname of a program interpreter.
957 a loadable segment that includes the section, the section's attributes will
961 Otherwise, that bit will be off.
962 This section is of type
965 This section holds line number information for symbolic debugging, which
966 describes the correspondence between the program source and the machine code.
967 The contents are unspecified.
968 This section is of type
970 No attribute types are used.
972 This section holds information in the
974 format described below.
975 This section is of type
977 No attribute types are used.
979 This section holds the procedure linkage table.
980 This section is of type
982 The attributes are processor-specific.
984 This section holds relocation information as described below.
986 has a loadable segment that includes relocation, the section's attributes
990 Otherwise the bit will be off.
993 is supplied by the section to which the relocations apply.
997 normally would have the name
999 This section is of type
1002 This section holds relocation information as described below.
1004 has a loadable segment that includes relocation, the section's attributes
1008 Otherwise the bit will be off.
1011 is supplied by the section to which the relocations apply.
1015 normally would have the name
1017 This section is of type
1020 This section holds read-only data that typically contributes to a
1021 non-writable segment in the process image.
1022 This section is of type
1024 The attribute used is
1027 This section hold read-only data that typically contributes to a
1028 non-writable segment in the process image.
1029 This section is of type
1031 The attribute used is
1034 This section holds section names.
1035 This section is of type
1037 No attribute types are used.
1039 This section holds strings, most commonly the strings that represent the
1040 names associated with symbol table entries.
1041 If the file has a loadable
1042 segment that includes the symbol string table, the section's attributes
1046 Otherwise the bit will be off.
1047 This section is of type
1050 This section holds a symbol table.
1051 If the file has a loadable segment
1052 that includes the symbol table, the section's attributes will include
1056 Otherwise the bit will be off.
1057 This section is of type
1060 This section holds the
1062 or executable instructions, of a program.
1063 This section is of type
1065 The attributes used are
1070 This section holds information about Java classes that must
1073 This section holds information used for C++ exception-handling.
1076 String table sections hold null-terminated character sequences, commonly
1078 The object file uses these strings to represent symbol
1080 One references a string as an index into the string
1082 The first byte, which is index zero, is defined to hold
1084 Similarly, a string table's last byte is defined to
1085 hold a null character, ensuring null termination for all strings.
1087 An object file's symbol table holds information needed to locate and
1088 relocate a program's symbolic definitions and references.
1090 index is a subscript into this array.
1092 .Bd -literal -offset indent
1095 Elf32_Addr st_value;
1097 unsigned char st_info;
1098 unsigned char st_other;
1099 Elf32_Half st_shndx;
1103 .Bd -literal -offset indent
1106 unsigned char st_info;
1107 unsigned char st_other;
1108 Elf64_Half st_shndx;
1109 Elf64_Addr st_value;
1110 Elf64_Xword st_size;
1114 .Bl -tag -width "st_value" -compact
1116 This member holds an index into the object file's symbol string table,
1117 which holds character representations of the symbol names.
1119 is non-zero, it represents a string table index that gives the symbol
1121 Otherwise, the symbol table has no name.
1123 This member gives the value of the associated symbol.
1125 Many symbols have associated sizes.
1126 This member holds zero if the symbol
1127 has no size or an unknown size.
1129 This member specifies the symbol's type and binding attributes:
1131 .Bl -tag -width "STT_SECTION" -compact
1133 The symbol's type is not defined.
1135 The symbol is associated with a data object.
1137 The symbol is associated with a function or other executable code.
1139 The symbol is associated with a section.
1140 Symbol table entries of
1141 this type exist primarily for relocation and normally have
1145 By convention the symbol's name gives the name of the source file
1146 associated with the object file.
1149 bindings, its section index is
1151 and it precedes the other
1153 symbols of the file, if it is present.
1155 This value up to and including
1157 are reserved for processor-specific semantics.
1159 This value down to and including
1161 are reserved for processor-specific semantics.
1164 .Bl -tag -width "STB_GLOBAL" -compact
1166 Local symbols are not visible outside the object file containing their
1168 Local symbols of the same name may exist in multiple file
1169 without interfering with each other.
1171 Global symbols are visible to all object files being combined.
1173 definition of a global symbol will satisfy another file's undefined
1174 reference to the same symbol.
1176 Weak symbols resemble global symbols, but their definitions have lower
1179 This value up to and including
1181 are reserved for processor-specific semantics.
1183 This value down to and including
1185 are reserved for processor-specific semantics.
1187 There are macros for packing and unpacking the binding and type fields:
1189 .Bl -tag -width "ELF32_ST_INFO(bind, type)" -compact
1191 .Fn ELF32_ST_BIND info
1194 .Fn ELF64_ST_BIND info
1195 extract a binding from an st_info value.
1197 .Fn ELF64_ST_TYPE info
1200 .Fn ELF32_ST_TYPE info
1201 extract a type from an st_info value.
1203 .Fn ELF32_ST_INFO bind type
1206 .Fn ELF64_ST_INFO bind type
1207 convert a binding and a type into an st_info value.
1212 This member currently holds zero and has no defined meaning.
1214 Every symbol table entry is
1216 in relation to some section.
1217 This member holds the relevant section
1221 Relocation is the process of connecting symbolic references with
1222 symbolic definitions.
1223 Relocatable files must have information that
1224 describes how to modify their section contents, thus allowing executable
1225 and shared object files to hold the right information for a process'
1227 Relocation entries are these data.
1229 Relocation structures that do not need an addend:
1231 .Bd -literal -offset indent
1233 Elf32_Addr r_offset;
1237 .Bd -literal -offset indent
1239 Elf64_Addr r_offset;
1244 Relocation structures that need an addend:
1246 .Bd -literal -offset indent
1248 Elf32_Addr r_offset;
1250 Elf32_Sword r_addend;
1253 .Bd -literal -offset indent
1255 Elf64_Addr r_offset;
1257 Elf64_Sxword r_addend;
1261 .Bl -tag -width "r_offset" -compact
1263 This member gives the location at which to apply the relocation action.
1264 For a relocatable file, the value is the byte offset from the beginning
1265 of the section to the storage unit affected by the relocation.
1267 executable file or shared object, the value is the virtual address of
1268 the storage unit affected by the relocation.
1270 This member gives both the symbol table index with respect to which the
1271 relocation must be made and the type of relocation to apply.
1273 types are processor-specific.
1274 When the text refers to a relocation
1275 entry's relocation type or symbol table index, it means the result of
1277 .Sy ELF_[32|64]_R_TYPE
1279 .Sy ELF[32|64]_R_SYM ,
1280 respectively to the entry's
1284 This member specifies a constant addend used to compute the value to be
1285 stored into the relocatable field.
1297 .%B Elf-64 Object File Format
1300 .%A Santa Cruz Operation
1301 .%B System V Application Binary Interface
1304 .%A Unix System Laboratories
1306 .%B "Executable and Linking Format (ELF)"
1309 The ELF header files made their appearance in
1311 ELF in itself first appeared in
1313 The ELF format is an adopted standard.
1315 This manual page was written by
1316 .An Jeroen Ruigrok van der Werven
1317 .Aq asmodai@FreeBSD.org
1318 with inspiration from BSDi's