Section Headers
An object file's section header table allows you to locate all of the sections of the file. The section header table is an array of Elf32_Shdr
or Elf64_Shdr
structures. A section header table index is a subscript into this array. The ELF header's e_shoff
member indicates the byte offset from the beginning of the file to the section header table. The e_shnum
member indicates how many entries that the section header table contains. The e_shentsize
member indicates the size in bytes of each entry.
If the number of sections is greater than or equal to SHN_LORESERVE
(0xff00
), e_shnum
has the value SHN_UNDEF
(0
). The actual number of section header table entries is contained in the sh_size
field of the section header at index 0
. Otherwise, the sh_size
member of the initial entry contains the value zero. See Extended Section Header.
Some section header table indexes are reserved in contexts where index size is restricted. For example, the st_shndx
member of a symbol table entry and the e_shnum
and e_shstrndx
members of the ELF header. In such contexts, the reserved values do not represent actual sections in the object file. Also in such contexts, an escape value indicates that the actual section index is to be found elsewhere, in a larger field.
Table 14-4 ELF Special Section Indexes
Name | Value |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Note:
Although index0
is reserved as the undefined value, the section header table contains an entry for index 0
. That is, if the e_shnum
member of the ELF header indicates a file has 6
entries in the section header table, the sections have the indexes 0
through 5
. The contents of the initial entry are specified later in this section.
-
SHN_UNDEF
-
An undefined, missing, irrelevant, or otherwise meaningless section reference. For example, a symbol defined relative to section number
SHN_UNDEF
is an undefined symbol. -
SHN_LORESERVE
-
The lower boundary of the range of reserved indexes.
-
SHN_LOPROC
-SHN_HIPROC
-
Values in this inclusive range are reserved for processor-specific semantics.
-
SHN_LOOS
-SHN_HIOS
-
Values in this inclusive range are reserved for operating system-specific semantics.
-
SHN_LOSUNW
-SHN_HISUNW
-
Values in this inclusive range are reserved for Sun-specific semantics.
-
SHN_SUNW_IGNORE
-
This section index provides a temporary symbol definition within relocatable objects. Reserved for internal use by
dtrace
(8). -
SHN_BEFORE, SHN_AFTER
-
Provide for initial and final section ordering in conjunction with
SHF_LINK_ORDER
section flags. See Table 14-7.SHN_BEFORE
andSHN_AFTER
are incompatible with objects that use extended section indexes. They are considered deprecated, and their use is discouraged. See Extended Section Header. -
SHN_AMD64_LCOMMON
-
x64 specific common block label. This label is similar to
SHN_COMMON
, but provides for identifying a large common block. -
SHN_ABS
-
Absolute values for the corresponding reference. For example, symbols defined relative to section number
SHN_ABS
have absolute values and are not affected by relocation. -
SHN_COMMON
-
Symbols defined relative to this section are common symbols, such as FORTRAN
COMMON
or unallocated C external variables. These symbols are sometimes referred to as tentative. -
SHN_XINDEX
-
An escape value indicating that the actual section header index is too large to fit in the containing field. The header section index is found in another location specific to the structure where the section index appears. See Extended Section Header.
-
SHN_HIRESERVE
-
The upper boundary of the range of reserved indexes. The system reserves indexes between
SHN_LORESERVE
andSHN_HIRESERVE
, inclusive. The values do not reference the section header table. The section header table does not contain entries for the reserved indexes.
Sections contain all information in an object file except the ELF header, the program header table, and the section header table. Moreover, the sections in object files satisfy several conditions.
-
Every section in an object file has exactly one section header describing the section. Section headers can exist that do not have a section.
-
Each section occupies one contiguous, possibly empty, sequence of bytes within a file.
-
Sections in a file cannot overlap. No byte in a file resides in more than one section.
-
An object file can have inactive space. The various headers and the sections might not cover every byte in an object file. The contents of the inactive data are unspecified.
A section header has the following structure. See sys/elf.h
.
typedef struct { elf32_Word sh_name; Elf32_Word sh_type; Elf32_Word sh_flags; Elf32_Addr sh_addr; Elf32_Off sh_offset; Elf32_Word sh_size; Elf32_Word sh_link; Elf32_Word sh_info; Elf32_Word sh_addralign; Elf32_Word sh_entsize; } Elf32_Shdr; typedef struct { Elf64_Word sh_name; Elf64_Word sh_type; Elf64_Xword sh_flags; Elf64_Addr sh_addr; Elf64_Off sh_offset; Elf64_Xword sh_size; Elf64_Word sh_link; Elf64_Word sh_info; Elf64_Xword sh_addralign; Elf64_Xword sh_entsize; } Elf64_Shdr;
-
sh_name
-
The name of the section. This members value is an index into the section header string table section giving the location of a null-terminated string. Section names and their descriptions are listed in ELF Special Sections.
-
sh_type
-
Categorizes the section's contents and semantics. Section types and their descriptions are listed in Table 14-5.
-
sh_flags
-
Sections support 1-bit flags that describe miscellaneous attributes. Flag definitions are listed in Table 14-7.
-
sh_addr
-
If the section appears in the memory image of a process, this member gives the address at which the section's first byte should reside. Otherwise, the member contains the value zero.
-
sh_offset
-
The byte offset from the beginning of the file to the first byte in the section. For a
SHT_NOBITS
section, this member indicates the conceptual offset in the file, as the section occupies no space in the file. -
sh_size
-
The section's size in bytes. Unless the section type is
SHT_NOBITS
, the section occupiessh_size
bytes in the file. A section of typeSHT_NOBITS
can have a nonzero size, but the section occupies no space in the file. -
sh_link
-
A section header table index link, whose interpretation depends on the section type. Table 14-8 describes the values.
-
sh_info
-
Extra information, whose interpretation depends on the section type. Table 14-8 describes the values. If the
sh_flags
field for this section header includes the attributeSHF_INFO_LINK
, then this member represents a section header table index. -
sh_addralign
-
Some sections have address alignment constraints. For example, if a section holds a double-word, the system must ensure double-word alignment for the entire section. In this case, the value of
sh_addr
must be congruent to0
, modulo the value ofsh_addralign
. Currently, only0
and positive integral powers of two are allowed. Values0
and1
mean the section has no alignment constraints. -
sh_entsize
-
Some sections hold a table of fixed-size entries, such as a symbol table. For such a section, this member gives the size in bytes of each entry. The member contains the value zero if the section does not hold a table of fixed-size entries.
A section header's sh_type
member specifies the section's semantics, as shown in the following table.
Table 14-5
ELF Section Types, sh_type
Name | Value |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
-
SHT_NULL
-
Identifies the section header as inactive. This section header does not have an associated section. Other members of the section header have undefined values.
-
SHT_PROGBITS
-
Identifies information defined by the program, whose format and meaning are determined solely by the program.
-
SHT_SYMTAB
,SHT_DYNSYM
,SHT_SUNW_LDYNSYM
-
Identifies a symbol table. Typically, a
SHT_SYMTAB
section provides symbols for link-editing. As a complete symbol table, the table can contain many symbols that are unnecessary for dynamic linking. Consequently, an object file can also contain aSHT_DYNSYM
section, which holds a minimal set of dynamic linking symbols, to save space.SHT_DYNSYM
can also be augmented with aSHT_SUNW_LDYNSYM
section. This additional section provides local function symbols to the runtime environment, but is not required for dynamic linking. This section allows debuggers to produce accurate stack traces in runtime contexts when the non-allocableSHT_SYMTAB
is not available, or has been stripped from the file. This section also provides the runtime environment with additional symbolic information for use withdladdr
(3C).When both a
SHT_SUNW_LDYNSYM
section and aSHT_DYNSYM
section exist, the link-editor places their data regions immediately adjacent to each other. TheSHT_SUNW_LDYNSYM
section precedes theSHT_DYNSYM
section. This placement allows the two tables to be viewed as a single larger contiguous symbol table, containing a reduced set of symbols fromSHT_SYMTAB
.See Symbol Table Section for details.
-
SHT_STRTAB
,SHT_DYNSTR
-
Identifies a string table. An object file can have multiple string table sections. See String Table Section for details.
-
SHT_RELA
-
Identifies relocation entries with explicit addends, such as type
Elf32_Rela
for the 32-bit class of object files. An object file can have multiple relocation sections. See Relocation Sections for details. -
SHT_HASH
-
Identifies a symbol hash table. A dynamically linked object file must contain a symbol hash table. Currently, an object file can have only one hash table, but this restriction might be relaxed in the future. See Hash Table Section for details.
-
SHT_DYNAMIC
-
Identifies information for dynamic linking. Currently, an object file can have only one dynamic section. See Dynamic Section for details.
-
SHT_NOTE
-
Identifies information that marks the file in some way. See Note Section for details.
-
SHT_NOBITS
-
Identifies a section that occupies no space in the file but otherwise resembles
SHT_PROGBITS
. Although this section contains no bytes, thesh_offset
member contains the conceptual file offset. -
SHT_REL
-
Identifies relocation entries without explicit addends, such as type
Elf32_Rel
for the 32-bit class of object files. An object file can have multiple relocation sections. See Relocation Sections for details. -
SHT_SHLIB
-
Identifies a reserved section which has unspecified semantics. Programs that contain a section of this type do not conform to the ABI.
-
SHT_INIT_ARRAY
-
Identifies a section containing an array of pointers to initialization functions. Each pointer in the array is taken as a parameterless procedure with a void return. See Initialization and Termination Sections for details.
-
SHT_FINI_ARRAY
-
Identifies a section containing an array of pointers to termination functions. Each pointer in the array is taken as a parameterless procedure with a void return. See Initialization and Termination Sections for details.
-
SHT_PREINIT_ARRAY
-
Identifies a section containing an array of pointers to functions that are invoked before all other initialization functions. Each pointer in the array is taken as a parameterless procedure with a void return. See Initialization and Termination Sections for details.
-
SHT_GROUP
-
Identifies a section group. A section group identifies a set of related sections that must be treated as a unit by the link-editor. Sections of type
SHT_GROUP
can appear only in relocatable objects. See Group Section for details. -
SHT_SYMTAB_SHNDX
-
Identifies a section containing extended section indexes, that are associated with a symbol table. If any section header indexes referenced by a symbol table, contain the escape value
SHN_XINDEX
(0xffff
), an associatedSHT_SYMTAB_SHNDX
entry is required. See Extended Section Header. -
SHT_LOOS
–SHT_HIOS
-
Values in this inclusive range are reserved for operating system-specific semantics.
-
SHT_LOSUNW
–SHT_HISUNW
-
Values in this inclusive range are reserved for Oracle Solaris OS semantics.
-
SHT_SUNW_symnsort
-
An array of indices into an associated symbol table, either
SHT_SYMTAB
, or the dynamic symbol table that is formed by adjacentSHT_SUNW_LDYNSYM
andSHT_DYNSYM
sections. When associated to the dynamic symbol table, these indices are relative to the start of theSHT_SUNW_LDYNSYM
section. The indices reference those symbols that contain memory addresses. The indices are sorted such that the indices reference the symbols by name, in lexical sort order. -
SHT_SUNW_phname
-
An array of string table indices, one per program header element, that associate program headers to names within the dynamic string table. See Program Header Name Section for details.
-
SHT_SUNW_ancillary
-
Indicates that the object is part of a group of ancillary objects. Contains information required to identify all the files that make up the group. See Ancillary Section for details.
-
SHT_SUNW_capchain
-
An array of indices that collect capability family members. The first element of the array is the chain version number. Following this element are a chain of
0
terminated capability symbol indices. Each0
terminated group of indices represents a capabilities family. The first element of each family is the capabilities lead symbol. The following elements point to family members. See Capabilities Section for details. -
SHT_SUNW_capinfo
-
An array of indices that associate symbol table entries to capabilities requirements, and their lead capabilities symbol. An object that defines symbol capabilities contains a
SHT_SUNW_cap
section. TheSHT_SUNW_cap
section header information points to the associatedSHT_SUNW_capinfo
section. TheSHT_SUNW_capinfo
section header information points to the associated symbol table section. See Capabilities Section for details. -
SHT_SUNW_symsort
-
An array of indices into an associated symbol table, either
SHT_SYMTAB
, or the dynamic symbol table that is formed by adjacentSHT_SUNW_LDYNSYM
andSHT_DYNSYM
sections. When associated to the dynamic symbol table, these indices are relative to the start of theSHT_SUNW_LDYNSYM
section. The indices reference those symbols that contain memory addresses. The indices are sorted such that the indices reference the symbols by increasing address. -
SHT_SUNW_tlssort
-
An array of indices into an associated symbol table, either
SHT_SYMTAB
, or the dynamic symbol table that is formed by adjacentSHT_SUNW_LDYNSYM
andSHT_DYNSYM
sections. When associated to the dynamic symbol table, these indices are relative to the start of theSHT_SUNW_LDYNSYM
section. The indices reference thread-local storage symbols. See Thread-Local Storage. The indices are sorted such that the indices reference the symbols by increasing offset. -
SHT_SUNW_LDYNSYM
-
Dynamic symbol table for non-global symbols. See previous
SHT_SYMTAB
,SHT_DYNSYM
,SHT_SUNW_LDYNSYM
description. -
SHT_SUNW_dof
-
Reserved for internal use by
dtrace
(8). -
SHT_SUNW_cap
-
Specifies capability requirements. See Capabilities Section for details.
-
SHT_SUNW_SIGNATURE
-
Identifies module verification signature.
-
SHT_SUNW_ANNOTATE
-
The processing of an annotate section follows all of the default rules for processing a section. The only exception occurs if the annotate section is in non-allocatable memory. If the section header flag
SHF_ALLOC
is not set, the link-editor silently ignores any unsatisfied relocations against this section. -
SHT_SUNW_DEBUGSTR
,SHT_SUNW_DEBUG
-
Identifies debugging information. Sections of this type are stripped from the object using the link-editor's
-z strip-class
option, or after the link-edit usingstrip
(1). -
SHT_SUNW_move
-
Identifies data to handle partially initialized symbols. See Move Section for details.
-
SHT_SUNW_COMDAT
-
Identifies a section that allows multiple copies of the same data to be reduced to a single copy. See COMDAT Section for details.
-
SHT_SUNW_syminfo
-
Identifies additional symbol information. See Syminfo Table Section for details.
-
SHT_SUNW_verdef
-
Identifies fine-grained versions defined by this file. See Version Definition Section for details.
-
SHT_SUNW_verneed
-
Identifies fine-grained dependencies required by this file. See Version Dependency Section for details.
-
SHT_SUNW_versym
-
Identifies a table describing the relationship of symbols to the version definitions offered by the file. See Version Symbol Section for details.
-
SHT_LOPROC
-SHT_HIPROC
-
Values in this inclusive range are reserved for processor-specific semantics.
-
SHT_SPARC_GOTDATA
-
Identifies SPARC specific data, referenced using
GOT
-relative addressing. That is, offsets relative to the address assigned to the symbol_GLOBAL_OFFSET_TABLE_
. For 64-bit SPARC, data in this section must be bound at link-edit time to locations within{+-} 2^32
bytes of theGOT
address. -
SHT_AMD64_UNWIND
-
Identifies x64 specific data, containing unwind function table entries for stack unwinding.
-
SHT_LOUSER
-
Specifies the lower boundary of the range of indexes that are reserved for application programs.
-
SHT_HIUSER
-
Specifies the upper boundary of the range of indexes that are reserved for application programs. Section types between
SHT_LOUSER
andSHT_HIUSER
can be used by the application without conflicting with current or future system-defined section types.
Other section-type values are reserved. As mentioned before, the section header for index 0
(SHN_UNDEF
) exists, even though the index marks undefined section references. The following table shows the values.
Table 14-6
ELF Section Header Table Entry: Index 0
Name | Value | Note |
---|---|---|
|
|
No name |
|
|
Inactive |
|
|
No flags |
|
|
No address |
|
|
No file offset |
|
|
No size |
|
|
No link information |
|
|
No auxiliary information |
|
|
No alignment |
|
|
No entries |
Should the number of sections or program headers exceed the ELF header data sizes, elements of section header 0
are used to define extended ELF header attributes. See Extended Section Header.
A section header's sh_flags
member holds 1-bit flags that describe the section's attributes.
Table 14-7 ELF Section Attribute Flags
Name | Value |
---|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
If a flag bit is set in sh_flags
, the attribute is on for the section. Otherwise, the attribute is off, or does not apply. Undefined attributes are reserved and are set to zero.
-
SHF_WRITE
-
Identifies a section that should be writable during process execution.
-
SHF_ALLOC
-
Identifies a section that occupies memory during process execution. Some control sections do not reside in the memory image of an object file. This attribute is off for those sections.
-
SHF_EXECINSTR
-
Identifies a section that contains executable machine instructions.
-
SHF_MERGE
-
Identifies a section containing data that can be merged to eliminate duplication. Unless the
SHF_STRINGS
flag is also set, the data elements in the section are of a uniform size. The size of each element is specified in the section header'ssh_entsize
field. If theSHF_STRINGS
flag is also set, the data elements consist of null-terminated character strings. The size of each character is specified in the section header'ssh_entsize
field. -
SHF_STRINGS
-
Identifies a section that consists of null-terminated character strings. The size of each character is specified in the section header's
sh_entsize
field. -
SHF_INFO_LINK
-
This section header's
sh_info
field holds a section header table index. -
SHF_LINK_ORDER
-
This section adds special ordering requirements for link-editors. The requirements apply to the referenced section identified by the
sh_link
field of this section's header. If this section is combined with other sections in the output file, the section must appear in the same relative order with respect to those sections, as the referenced section appears with respect to sections the referenced section is combined with. The linked-to section must be unordered, and cannot in turn specifySHF_LINK_ORDER
orSHF_ORDERED
.A typical use of this flag is to build a table that references text or data sections in address order.
In addition to adding ordering requirements,
SHF_LINK_ORDER
indicates that the section contains metadata describing the referenced section. When performing unused section elimination, the link editor ensures that both the section and the referenced section are retained or discarded together. Relocations from anSHF_LINK_ORDER
section to its referenced section do not, by themselves, indicate that the referenced section is used.In the absence of the
sh_link
ordering information, sections from a single input file combined within one section of the output file are contiguous. These sections have the same relative ordering as the sections did in the input file. The contributions from multiple input files appear in link-line order.Note:
The specialsh_link
valuesSHN_BEFORE
andSHN_AFTER
imply that the sorted section is to precede or follow, respectively, all other sections in the set being ordered. See Table 14-4. Input file link-line order is preserved if multiple sections in an ordered set have one of these special values.SHN_BEFORE
andSHN_AFTER
are incompatible with objects that use extended section indexes. They are considered deprecated, and their use is discouraged. See Extended Section Header. -
SHF_OS_NONCONFORMING
-
This section requires special OS-specific processing beyond the standard linking rules to avoid incorrect behavior. If this section has either an
sh_type
value or containssh_flags
bits in the OS-specific ranges for those fields, and the link-editor does not recognize these values, then the object file containing this section is rejected with an error. -
SHF_GROUP
-
This section is a member, perhaps the only member, of a section group. The section must be referenced by a section of type
SHT_GROUP
. TheSHF_GROUP
flag can be set only for sections that are contained in relocatable objects. See Group Section for details. -
SHF_TLS
-
This section holds thread-local storage. Each thread within a process has a distinct instance of this data. See Thread-Local Storage for details.
-
SHF_COMPRESSED
-
Identifies a section containing compressed data.
SHF_COMPRESSED
applies only to non-allocable sections, and cannot be used in conjunction withSHF_ALLOC
. In addition,SHF_COMPRESSED
cannot be applied to sections of typeSHT_NOBITS
. See Section Compression for details. -
SHF_MASKOS
-
All bits that are included in this mask are reserved for operating system-specific semantics.
-
SHF_SUNW_NODISCARD
-
The link-editor's
-z discard-unused
option can result in unreferencedSHF_ALLOC
sections being discarded from a link-edit.SHF_SUNW_NODISCARD
ensures that anSHF_ALLOC
section is not discarded using the-z discard-unused
option, even if the section is unreferenced. -
SHF_SUNW_ABSENT
-
Indicates that the data for this section is not present in this file. When ancillary objects are created, the primary object and any ancillary objects, all have the same section header array. This organization facilitates the merging of the information contained in these objects, and allows the use of a single symbol table. Each file contains a subset of the section data. The data for allocable sections is written to the primary object while the data for non-allocable sections is written to an ancillary file. The
SHF_SUNW_ABSENT
flag indicates that the data for the section is not present in the object being examined. When theSHF_SUNW_ABSENT
flag is set, thesh_size
field of the section header must be 0. An application encountering anSHF_SUNW_ABSENT
section can choose to ignore the section, or to search for the section data within one of the related ancillary files. See Debugger Access and Use of Ancillary Objects. -
SHF_SUNW_PRIMARY
-
The default behavior when ancillary objects are created is to write all allocable sections to the primary object and all non-allocable sections to the ancillary objects. The
SHF_SUNW_PRIMARY
flag overrides this behavior. Any output section containing one more input section with theSHF_SUNW_PRIMARY
flag set is written to the primary object. -
SHF_MASKPROC
-
All bits that are included in this mask are reserved for processor-specific semantics.
-
SHF_AMD64_LARGE
-
The default compilation model for x64 only provides for 32-bit displacements. This displacement limits the size of sections, and eventually segments, to 2 Gbytes. This attribute flag identifies a section that can hold more than 2 Gbyte. This flag allows the linking of object files that use different code models.
An x64 object file section that does not contain the
SHF_AMD64_LARGE
attribute flag can be freely referenced by objects using small code models. A section that contains this flag can only be referenced by objects that use larger code models. For example, an x64 medium code model object can refer to data in sections that contain the attribute flag and sections that do not contain the attribute flag. However, an x64 small code model object can only refer to data in a section that does not contain this flag. -
SHF_ORDERED
-
SHF_ORDERED
is an older version of the functionality provided bySHF_LINK_ORDER
, and has been superseded bySHF_LINK_ORDER
.SHF_ORDERED
is no longer supported. The following information is provided for historical context.SHF_ORDERED
offers two distinct and separate abilities. First, an output section can be specified, and second, special ordering requirements are required from the link-editor.The
sh_link
field of anSHF_ORDERED
section forms a linked list of sections. This list is terminated by a final section with ash_link
that points at itself. All sections in this list are assigned to the output section with the name of the final section in the list.If the
sh_info
entry of the ordered section is a valid section within the same input file, the ordered section is sorted based on the relative ordering within the output file of the section pointed to by thesh_info
entry. The section pointed at by thesh_info
entry must be unordered, and cannot in turn specifySHF_LINK_ORDER
orSHF_ORDERED
.In the absence of the
sh_info
ordering information, sections from a single input file combined within one section of the output file are contiguous. These sections have the same relative ordering as the sections appear in the input file. The contributions from multiple input files appear in link-line order.Note:
The specialsh_info
valuesSHN_BEFORE
andSHN_AFTER
imply that the sorted section is to precede or follow, respectively, all other sections in the set being ordered. See Table 14-4. Input file link-line order is preserved if multiple sections in an ordered set have one of these special values.SHN_BEFORE
andSHN_AFTER
are incompatible with objects that use extended section indexes. They are considered deprecated, and their use is discouraged. See Extended Section Header. -
SHF_EXCLUDE
-
This section is excluded from input to the link-edit of an executable or shared object. This flag is ignored if the
SHF_ALLOC
flag is also set, or if relocations exist against the section.
Two members in the section header, sh_link
and sh_info
, hold special information, depending on section type.
Table 14-8
ELF
sh_link
and sh_info
Interpretation
sh_type | sh_link | sh_info |
---|---|---|
|
The section header index of the associated string table. |
|
|
The section header index of the associated symbol table. |
|
|
The section header index of the associated symbol table. |
The section header index of the section to which the relocation applies, otherwise |
|
The section header index of the associated string table. |
One greater than the symbol table index of the last local symbol, |
|
The section header index of the associated symbol table. |
The symbol table index of an entry in the associated symbol table. The name of the specified symbol table entry provides a signature for the section group. |
|
The section header index of the associated symbol table. |
|
|
The section header index of the associated symbol table. |
|
|
The section header index of the associated string table. This index is the same string table used by the |
|
|
The section header index of the associated string table. |
|
|
If symbol capabilities exist, the section header index of the associated |
If any capabilities refer to named strings, the section header index of the associated string table, otherwise |
|
The section header index of the associated symbol table. |
For a dynamic object, the section header index of the associated |
|
The section header index of the associated symbol table. |
|
|
The section header index of the associated symbol table. |
|
|
The section header index of the associated string table. This index is the same string table used by the |
One greater than the symbol table index of the last local symbol, |
|
The section header index of the associated symbol table. |
|
|
|
|
|
The section header index of the associated symbol table. |
The section header index of the associated |
|
The section header index of the associated string table. |
The number of version definitions within the section. |
|
The section header index of the associated string table. |
The number of version dependencies within the section. |
|
The section header index of the associated symbol table. |
|