我在读有关章节和片段。 看来你可以列出节和段之间的映射如下。
$ readelf -l test
Elf file type is EXEC (Executable file)
Entry point 0x8048330
There are 9 program headers, starting at offset 52
Program Headers:
Type Offset VirtAddr PhysAddr FileSiz MemSiz Flg Align
PHDR 0x000034 0x08048034 0x08048034 0x00120 0x00120 R E 0x4
INTERP 0x000154 0x08048154 0x08048154 0x00013 0x00013 R 0x1
[Requesting program interpreter: /lib/ld-linux.so.2]
LOAD 0x000000 0x08048000 0x08048000 0x0065c 0x0065c R E 0x1000
LOAD 0x000f14 0x08049f14 0x08049f14 0x00104 0x00110 RW 0x1000
DYNAMIC 0x000f28 0x08049f28 0x08049f28 0x000c8 0x000c8 RW 0x4
NOTE 0x000168 0x08048168 0x08048168 0x00044 0x00044 R 0x4
GNU_EH_FRAME 0x000564 0x08048564 0x08048564 0x00034 0x00034 R 0x4
GNU_STACK 0x000000 0x00000000 0x00000000 0x00000 0x00000 RW 0x4
GNU_RELRO 0x000f14 0x08049f14 0x08049f14 0x000ec 0x000ec R 0x1
Section to Segment mapping:
Segment Sections...
00
01 .interp
02 .interp .note.ABI-tag .note.gnu.build-id .gnu.hash .dynsym .dynstr .gnu.version .gnu.version_r .rel.dyn .rel.plt .init .plt .text .fini .rodata .eh_frame_hdr .eh_frame
03 .ctors .dtors .jcr .dynamic .got .got.plt .data .bss
04 .dynamic
05 .note.ABI-tag .note.gnu.build-id
06 .eh_frame_hdr
07
08 .ctors .dtors .jcr .dynamic .got
我的问题，
- 我不明白什么程序头是什么意思？ 他们是如何与段？
- 节到段的映射是明确的。 但可能有人的名字呢？ 我看到的只是数字。 我所标识的代码SEG（03），数据SEG（02）和叠层（07）。
要理解的输出readelf它会帮助你理解的格式ELF文件。 请参考此文档。
至于了解如何解释的输出readelf此链接可能会有所帮助。
至于你的第二个问题， 这个链接描述段。 在该文件中搜索“各种节举行的计划和控制信息：”发现那里的部分名称描述的区域。
该文件描述了如下细分：
各个部分保存程序和控制信息：
.bss This section holds uninitialized data that contributes to the
program's memory image. By definition, the system initializes the
data with zeros when the program begins to run. This section is of
type SHT_NOBITS. The attribute types are SHF_ALLOC and SHF_WRITE.
.comment This section holds version control information. This section is of
type SHT_PROGBITS. No attribute types are used.
.ctors This section holds initialized pointers to the C++ constructor
functions. This section is of type SHT_PROGBITS. The attribute
types are SHF_ALLOC and SHF_WRITE.
.data This section holds initialized data that contribute to the program's
memory image. This section is of type SHT_PROGBITS. The attribute
types are SHF_ALLOC and SHF_WRITE.
.data1 This section holds initialized data that contribute to the program's
memory image. This section is of type SHT_PROGBITS. The attribute
types are SHF_ALLOC and SHF_WRITE.
.debug This section holds information for symbolic debugging. The contents
are unspecified. This section is of type SHT_PROGBITS. No
attribute types are used.
.dtors This section holds initialized pointers to the C++ destructor
functions. This section is of type SHT_PROGBITS. The attribute
types are SHF_ALLOC and SHF_WRITE.
.dynamic 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. This section is of type
SHT_DYNAMIC. See the attributes above.
.dynstr This section holds strings needed for dynamic linking, most commonly
the strings that represent the names associated with symbol table
entries. This section is of type SHT_STRTAB. The attribute type
used is SHF_ALLOC.
.dynsym This section holds the dynamic linking symbol table. This section
is of type SHT_DYNSYM. The attribute used is SHF_ALLOC.
.fini This section holds executable instructions that contribute to the
process termination code. When a program exits normally the system
arranges to execute the code in this section. This section is of
type SHT_PROGBITS. The attributes used are SHF_ALLOC and
SHF_EXECINSTR.
.gnu.version
This section holds the version symbol table, an array of ElfN_Half
elements. This section is of type SHT_GNU_versym. The attribute
type used is SHF_ALLOC.
.gnu.version_d
This section holds the version symbol definitions, a table of
ElfN_Verdef structures. This section is of type SHT_GNU_verdef.
The attribute type used is SHF_ALLOC.
.gnu.version_r
This section holds the version symbol needed elements, a table of
ElfN_Verneed structures. This section is of type SHT_GNU_versym.
The attribute type used is SHF_ALLOC.
.got This section holds the global offset table. This section is of type
SHT_PROGBITS. The attributes are processor specific.
.hash This section holds a symbol hash table. This section is of type
SHT_HASH. The attribute used is SHF_ALLOC.
.init 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. This section is of type SHT_PROGBITS.
The attributes used are SHF_ALLOC and SHF_EXECINSTR.
.interp This section holds the pathname of a program interpreter. If the
file has a loadable segment that includes the section, the section's
attributes will include the SHF_ALLOC bit. Otherwise, that bit will
be off. This section is of type SHT_PROGBITS.
.line This section holds line number information for symbolic debugging,
which describes the correspondence between the program source and
the machine code. The contents are unspecified. This section is of
type SHT_PROGBITS. No attribute types are used.
.note This section holds information in the "Note Section" format. This
section is of type SHT_NOTE. No attribute types are used. OpenBSD
native executables usually contain a .note.openbsd.ident section to
identify themselves, for the kernel to bypass any compatibility ELF
binary emulation tests when loading the file.
.note.GNU-stack
This section is used in Linux object files for declaring stack
attributes. This section is of type SHT_PROGBITS. The only
attribute used is SHF_EXECINSTR. This indicates to the GNU linker
that the object file requires an executable stack.
.plt This section holds the procedure linkage table. This section is of
type SHT_PROGBITS. The attributes are processor specific.
.relNAME This section holds relocation information as described below. If
the file has a loadable segment that includes relocation, the
section's attributes will include the SHF_ALLOC bit. Otherwise the
bit will be off. By convention, "NAME" is supplied by the section
to which the relocations apply. Thus a relocation section for .text
normally would have the name .rel.text. This section is of type
SHT_REL.
.relaNAME This section holds relocation information as described below. If
the file has a loadable segment that includes relocation, the
section's attributes will include the SHF_ALLOC bit. Otherwise the
bit will be off. By convention, "NAME" is supplied by the section
to which the relocations apply. Thus a relocation section for .text
normally would have the name .rela.text. This section is of type
SHT_RELA.
.rodata This section holds read-only data that typically contributes to a
nonwritable segment in the process image. This section is of type
SHT_PROGBITS. The attribute used is SHF_ALLOC.
.rodata1 This section holds read-only data that typically contributes to a
nonwritable segment in the process image. This section is of type
SHT_PROGBITS. The attribute used is SHF_ALLOC.
.shstrtab This section holds section names. This section is of type
SHT_STRTAB. No attribute types are used.
.strtab 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. Otherwise the
bit will be off. This section is of type SHT_STRTAB.
.symtab This section holds a symbol table. If the file has a loadable
segment that includes the symbol table, the section's attributes
will include the SHF_ALLOC bit. Otherwise the bit will be off.
This section is of type SHT_SYMTAB.
.text This section holds the "text", or executable instructions, of a
program. This section is of type SHT_PROGBITS. The attributes used
are SHF_ALLOC and SHF_EXECINSTR.
在ELF二进制程序标题描述如何二进制应运行。 有趣的部分是LOAD头，其加载二进制文件的一部分在内存中分成不同的地方。 有可能是LOAD头的几乎任意数量的二进制，但通常连接把一切只读和可执行到一个和所有读/写到另一个。 有这将具有只读操作系统加载数据报头，读写数据和只读略有增加安全性的可执行代码。
段在这里仅仅意味着在内存不同的地方加载的二进制文件的部分。 所以基本上不同的负载报头。
部分是数据是如何在连接期间举办。 由于各种原因，你想有更好的粒度组织的事情不仅仅是数据/代码。 有些数据是只读的，它把在“.RODATA”在你的例子。 该代码是“的.text”，初始化的数据是“数据”，而变量是在程序启动归零数据都在“的.bss”。
所述“部分段映射”告诉您哪些部分是在其中段（不同LOAD标头）。 所以“的.text”和“.RODATA”是在第一负载报头（第三程序报头）和“数据”是在第二负载报头（第四程序报头）。
堆栈是什么，操作系统为您提供了执行，它不是由一个ELF二进制描述。
