gpt4 book ai didi

compiler-construction - 启动期间生成的 ELF 可执行段错误

转载 作者:行者123 更新时间:2023-12-04 01:50:04 26 4
gpt4 key购买 nike

我正在生成一个 ELF 可执行文件,其中一个 .text 部分加载到一个 LOAD 段中。它反汇编很好,但尝试在 gdb 下运行它会给出 During startup program terminated with signal SIGSEGV, Segmentation fault.

readelf 给出:

ELF Header:
Magic: 7f 45 4c 46 02 01 01 00 00 00 00 00 00 00 00 00
Class: ELF64
Data: 2's complement, little endian
Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: EXEC (Executable file)
Machine: Advanced Micro Devices X86-64
Version: 0x1
Entry point address: 0x400056
Start of program headers: 759 (bytes into file)
Start of section headers: 503 (bytes into file)
Flags: 0x0
Size of this header: 64 (bytes)
Size of program headers: 56 (bytes)
Number of program headers: 1
Size of section headers: 64 (bytes)
Number of section headers: 4
Section header string table index: 2

Section Headers:
[Nr] Name Type Address Offset
Size EntSize Flags Link Info Align
[ 0] NULL 0000000000000000 00000000
0000000000000000 0000000000000000 0 0 0
[ 1] .text PROGBITS 0000000000400040 00000040
000000000000005b 0000000000000000 AX 0 0 16
[ 2] .strtab STRTAB 0000000000000000 0000009b
000000000000009c 0000000000000000 0 0 4
[ 3] .symtab SYMTAB 0000000000000000 00000137
00000000000000c0 0000000000000018 2 1 4
Key to Flags:
W (write), A (alloc), X (execute), M (merge), S (strings), l (large)
I (info), L (link order), G (group), T (TLS), E (exclude), x (unknown)
O (extra OS processing required) o (OS specific), p (processor specific)

There are no section groups in this file.

Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000000040 0x0000000000400000 0x0000000000400000
0x000000000000009b 0x000000000000009b R E 200000

Section to Segment mapping:
Segment Sections...
00 .text

There is no dynamic section in this file.

There are no relocations in this file.

The decoding of unwind sections for machine type Advanced Micro Devices X86-64 is not currently supported.

Symbol table '.symtab' contains 8 entries:
Num: Value Size Type Bind Vis Ndx Name
0: 0000000000000000 0 NOTYPE LOCAL DEFAULT UND
1: 0000000000000000 0 FUNC GLOBAL DEFAULT 1
2: 0000000000400040 16 FUNC GLOBAL DEFAULT 1 _R_Potato
3: 0000000000400050 6 FUNC GLOBAL DEFAULT 1 _R_Main
4: 0000000000000000 0 SECTION LOCAL DEFAULT 1
5: 0000000000400056 18 FUNC GLOBAL DEFAULT 1 _start
6: 0000000000400068 25 FUNC GLOBAL DEFAULT 1 GetStringLength
7: 0000000000400081 26 FUNC GLOBAL DEFAULT 1 _R_Print

hexdump,如果需要,可以找到here .我假设问题出在内核试图映射 LOAD 段中的内容,但我没有发现问题。这是怎么回事?

最佳答案

Program Headers:
Type Offset VirtAddr PhysAddr
FileSiz MemSiz Flags Align
LOAD 0x0000000000000040 0x0000000000400000 0x0000000000400000
0x000000000000009b 0x000000000000009b R E 200000

这就是你的问题所在:你要求内核执行相当于 mmap(0x400000, 0x9b, PROT_READ|PROT_EXEC, MAP_FIXED, $fd, 0x40),但是这样的 mmap 调用总是会失败并返回 EINVAL,因为地址和偏移量不是等效的模对齐。

您希望文件偏移量为 0,而不是 0x40。也就是说,您的LOAD 段应该涵盖两者 Elf64_Ehdr 程序.text在一起(您的 LOAD 段的大小已经包括两者)。

关于compiler-construction - 启动期间生成的 ELF 可执行段错误,我们在Stack Overflow上找到一个类似的问题: https://stackoverflow.com/questions/40833756/

26 4 0
Copyright 2021 - 2024 cfsdn All Rights Reserved 蜀ICP备2022000587号
广告合作:1813099741@qq.com 6ren.com