Searched refs:PT_DYNAMIC (Results 1 – 25 of 75) sorted by relevance
123
2 ## dynamic table when it is not in a PT_DYNAMIC segment.14 …arning: '[[FILE]]': SHT_DYNAMIC section with index 1 is not contained within the PT_DYNAMIC segment15 # WARNING1: warning: '[[FILE]]': invalid PT_DYNAMIC size (0x1){{$}}16 # WARNING1: warning: '[[FILE]]': SHT_DYNAMIC section header and PT_DYNAMIC program header disagree …17 # WARNING1: warning: '[[FILE]]': PT_DYNAMIC dynamic table is invalid: SHT_DYNAMIC will be used57 - Type: PT_DYNAMIC71 …arning: '[[FILE]]': SHT_DYNAMIC section with index 1 is not contained within the PT_DYNAMIC segment110 - Type: PT_DYNAMIC115 ## Case 3: Both dynamic tables found using SHT_DYNAMIC/PT_DYNAMIC are corrupted.123 # WARNING3: warning: '[[FILE]]': invalid PT_DYNAMIC size (0x1){{$}}[all …]
1 ## If the offset and/or size fields of the PT_DYNAMIC field become corrupted,4 ## Case A: Test case where the size of the PT_DYNAMIC header is too large to fit in the file,8 ## broken PT_DYNAMIC header, check we dump the dynamic table.13 # WARN1: warning: '[[FILE]]': PT_DYNAMIC segment offset (0x1000) + file size (0x131) exceeds the si…31 # WARN1-NOHEADERS: warning: '[[FILE]]': PT_DYNAMIC segment offset (0x1000) + file size (0x12) excee…33 ## Case B: Test case where the offset of the PT_DYNAMIC header is too large to be in the file.36 ## broken PT_DYNAMIC header. Check we also report a warning about broken fields of the SH…43 # WARN2: warning: '[[FILE]]': PT_DYNAMIC segment offset (0x1131) + file size (0x10) exceeds the siz…56 ## Case C: test we report a warning when the offset + the file size of the PT_DYNAMIC is so large a100 # WARN5: warning: '[[FILE]]': PT_DYNAMIC segment offset (0xffffffff) + file size (0x8) exceeds the …[all …]
2 ## is not alone in PT_DYNAMIC segment.13 # WARNING: warning: '[[FILE]]': SHT_DYNAMIC section with index 2 is not at the start of PT_DYNAMIC …14 # WARNING: warning: '[[FILE]]': invalid PT_DYNAMIC size (0x21){{$}}15 # WARNING: warning: '[[FILE]]': SHT_DYNAMIC section header and PT_DYNAMIC program header disagree a…16 # WARNING: warning: '[[FILE]]': PT_DYNAMIC dynamic table is invalid: SHT_DYNAMIC will be used55 - Type: PT_DYNAMIC107 - Type: PT_DYNAMIC112 ## In this case .text goes after .dynamic, but (PT_DYNAMIC segment size % dynamic entry size != 0)119 # WARNING2: warning: '[[FILE]]': invalid PT_DYNAMIC size (0x101){{$}}120 # WARNING2: warning: '[[FILE]]': PT_DYNAMIC dynamic table is invalid: SHT_DYNAMIC will be used[all …]
31 - Type: PT_DYNAMIC73 - Type: PT_DYNAMIC
45 - Type: PT_DYNAMIC269 - Type: PT_DYNAMIC311 - Type: PT_DYNAMIC349 - Type: PT_DYNAMIC395 - Type: PT_DYNAMIC433 - Type: PT_DYNAMIC
10 # WARN: warning: '[[FILE]]': invalid PT_DYNAMIC size (0x4){{$}}19 # WARN-GNU: warning: '[[FILE]]': invalid PT_DYNAMIC size (0x4){{$}}42 - Type: PT_DYNAMIC84 - Type: PT_DYNAMIC178 - Type: PT_DYNAMIC235 - Type: PT_DYNAMIC277 - Type: PT_DYNAMIC374 - Type: PT_DYNAMIC468 - Type: PT_DYNAMIC
25 - Type: PT_DYNAMIC
34 - Type: PT_DYNAMIC199 - Type: PT_DYNAMIC231 - Type: PT_DYNAMIC260 - Type: PT_DYNAMIC292 - Type: PT_DYNAMIC321 - Type: PT_DYNAMIC
121 - Type: PT_DYNAMIC156 - Type: PT_DYNAMIC
28 dynamic PT_DYNAMIC FLAGS(4);46 # CHECK-NEXT: Type: PT_DYNAMIC74 # CHECK-N-NEXT: Type: PT_DYNAMIC
7 PHDRS { foo PT_DYNAMIC; }
18 dyn PT_DYNAMIC;
40 - Type: PT_DYNAMIC92 - Type: PT_DYNAMIC136 - Type: PT_DYNAMIC
35 - Type: PT_DYNAMIC
36 - Type: PT_DYNAMIC
41 - Type: PT_DYNAMIC
44 - Type: PT_DYNAMIC
39 - Type: PT_DYNAMIC
45 - Type: PT_DYNAMIC
42 - Type: PT_DYNAMIC
87 MC.phdr_dynamic.p_type = llvm::ELF::PT_DYNAMIC; in TEST()136 MC.phdr_dynamic.p_type = llvm::ELF::PT_DYNAMIC; in TEST()
51 - Type: PT_DYNAMIC
56 - Type: PT_DYNAMIC