The following sections are defined in the ELF reference specification.
Table 4-1.
| Name | Type | Attributes |
|---|---|---|
| .bss | SHT_NOTE | SHF_ALLOC+SHF_WRITE |
| .comment | SHT_NULL | 0 |
| .data | SHT_NULL | SHF_ALLOC+SHF_WRITE |
| .data1 | SHT_NULL | SHF_ALLOC+SHF_WRITE |
| .debug | SHT_NULL | 0 |
| .dynamic | SHT_HASH | SHF_ALLOC+SHF_WRITE |
| .dynstr | SHT_SYMTAB | SHF_ALLOC |
| .dynsym | SHT_SHLIB | SHF_ALLOC |
| .fini | SHT_NULL | SHF_ALLOC+SHF_EXECINSTR |
| .fini_array | SHF_ALLOC+SHF_WRITE | |
| .got | SHT_NULL | SHF_ALLOC+SHF_WRITE |
| .hash | SHT_RELA | SHF_ALLOC |
| .init | SHT_NULL | SHF_ALLOC+SHF_EXECINSTR |
| .init_array | SHF_ALLOC+SHF_WRITE | |
| .interp | SHT_NULL | SHF_ALLOC |
| .line | SHT_NULL | 0 |
| .note | SHT_DYNAMIC | 0 |
| .plt | SHT_NULL | SHF_ALLOC+SHF_EXECINSTR |
| .preinit_array | SHF_ALLOC+SHF_WRITE | |
| .rel.bss | SHT_NOBITS | SHF_ALLOC |
| .rel.data | SHT_NOBITS | 0 |
| .rel.got | SHT_NOBITS | SHF_ALLOC |
| .rel.plt | SHT_NOBITS | SHF_ALLOC |
| .rel.text | SHT_NOBITS | 0 |
| .rodata | SHT_NULL | SHF_ALLOC |
| .rodata1 | SHT_NULL | SHF_ALLOC |
| .shstrtab | SHT_SYMTAB | 0 |
| .strtab | SHT_SYMTAB | SHF_ALLOC |
| .symtab | SHT_PROGBITS | SHF_ALLOC |
| .text | SHT_NULL | SHF_ALLOC+SHF_EXECINSTR |
This section holds uninitialized data that contribute to the program's memory image. By definition, the system initializes the data with zeros when the program begins to run. The section occupies no file space, as indicated by the section type, SHT_NOBITS
This section holds version control information.
This section holds initialized data that contribute to the program's memory image.
This section holds initialized data that contribute to the program's memory image.
This section holds information for symbolic debugging. The contents are unspecified. All section names with the prefix .debug are reserved for future use in the ABI.
This section holds dynamic linking information. The section's attributes will include the SHF_ALLOC bit. Whether the SHF_WRITE bit is set is processor specific. See Chapter 5 for more information.
This section holds strings needed for dynamic linking, most commonly the strings that represent the names associated with symbol table entries. See Chapter 5 for more information.
This section holds the dynamic linking symbol table, as described in `Symbol Table'. See Chapter 5 for more information.
This section holds executable instructions that contribute to the process termination code. That is, when a program exits normally, the system arranges to execute the code in this section.
This section holds an array of function pointers that contributes to a single termination array for the executable or shared object containing the section.
This section holds the global offset table. See `Coding Examples' in Chapter 3, `Special Sections' in Chapter 4, and `Global Offset Table' in Chapter 5 of the processor supplement for more information.
This section holds a symbol hash table. See `Hash Table' in Chapter 5 for more information.
This section holds executable instructions that contribute to the process initialization code. When a program starts to run, the system arranges to execute the code in this section before calling the main program entry point (called main for C programs)
This section holds an array of function pointers that contributes to a single initialization array for the executable or shared object containing the section.
This section holds the path name of a program interpreter. If the file has a loadable segment that includes relocation, the sections' attributes will include the SHF_ALLOC bit; otherwise, that bit will be off. See Chapter 5 for more information.
This section holds line number information for symbolic debugging, which describes the correspondence between the source program and the machine code. The contents are unspecified.
This section holds information in the format that `Note Section'. in Chapter 5 describes.
This section holds the procedure linkage table. See `Special Sections' in Chapter 4 and `Procedure Linkage Table' in Chapter 5 of the processor supplement for more information.
This section holds an array of function pointers that contributes to a single pre-initialization array for the executable or shared object containing the section.
This section holds relocation information, as described in `Relocation'. These relocations are applied to the .bss section.
This section holds relocation information, as described in `Relocation'. These relocations are applied to the .data section.
This section holds relocation information, as described in `Relocation'. These relocations are applied to the .got section.
This section holds relocation information, as described in `Relocation'. These relocations are applied to the .plt section.
This section holds relocation information, as described in `Relocation'. These relocations are applied to the .text section.
This section holds read-only data that typically contribute to a non-writable segment in the process image. See `Program Header' in Chapter 5 for more information.
This section hold sread-only data that typically contribute to a non-writable segment in the process image. See `Program Header' in Chapter 5 for more information.
This section holds section names.
This section holds strings, most commonly the strings that represent the names associated with symbol table entries. If the file has a loadable segment that includes the symbol string table, the section's attributes will include the SHF_ALLOC bit; otherwi
This section holds a symbol table, as `Symbol Table'. in this chapter describes. If the file has a loadable segment that includes the symbol table, the section's attributes will include the SHF_ALLOC bit; otherwise, that bit will be off.
This section holds the `text,' or executable instructions, of a program.