135 lines · yaml
1## Check how obj2yaml produces SHT_HASH section descriptions.2 3## Check that obj2yaml uses "Bucket" and "Chain" tags to describe4## a SHT_HASH section when it has content of a correct size.5## I.e. data size == 4 * (2 + nbucket + nchain).6 7# RUN: yaml2obj --docnum=1 %s -o %t18# RUN: obj2yaml %t1 | FileCheck %s --check-prefix=CHAIN-BUCKET9 10# CHAIN-BUCKET: - Name: .hash111# CHAIN-BUCKET-NEXT: Type: SHT_HASH12# CHAIN-BUCKET-NEXT: Bucket: [ 3 ]13# CHAIN-BUCKET-NEXT: Chain: [ 4, 5 ]14# CHAIN-BUCKET: - Name: .hash215# CHAIN-BUCKET-NEXT: Type: SHT_HASH16# CHAIN-BUCKET-NEXT: Bucket: [ ]17# CHAIN-BUCKET-NEXT: Chain: [ ]18 19--- !ELF20FileHeader:21 Class: ELFCLASS3222 Data: ELFDATA2LSB23 Type: ET_DYN24Sections:25## Case 1: A non-empty hash table: nbucket == 1, nchain == 2. 26 - Name: .hash127 Type: SHT_HASH28 Content: '0100000002000000030000000400000005000000'29## Case 2: An empty hash table: nbucket == 0, nchain == 0.30 - Name: .hash231 Type: SHT_HASH32 Content: '0000000000000000'33 34## Check that obj2yaml falls back to using the "Content" tag when35## hash sections are broken.36 37# RUN: yaml2obj --docnum=2 %s -o %t238# RUN: obj2yaml %t2 | FileCheck %s --check-prefix=CONTENT39 40# CONTENT: - Name: .empty_hash41# CONTENT-NEXT: Type: SHT_HASH42# CONTENT-NEXT: Content: ''43# CONTENT-NEXT: - Name: .invalid_header44# CONTENT-NEXT: Type: SHT_HASH45# CONTENT-NEXT: Content: '00'46# CONTENT-NEXT: - Name: .truncated47# CONTENT-NEXT: Type: SHT_HASH48# CONTENT-NEXT: Content: '01000000020000000300000004000000'49# CONTENT-NEXT: - Name: .oversized50# CONTENT-NEXT: Type: SHT_HASH51# CONTENT-NEXT: Content: '0100000002000000030000000400000000'52# CONTENT-NEXT: - Name: .overflow153# CONTENT-NEXT: Type: SHT_HASH54# CONTENT-NEXT: Content: 01000000FFFFFFFF{{$}}55# CONTENT-NEXT: - Name: .overflow256# CONTENT-NEXT: Type: SHT_HASH57# CONTENT-NEXT: Content: FFFFFFFF01000000{{$}}58# CONTENT-NEXT: ...59 60--- !ELF61FileHeader:62 Class: ELFCLASS3263 Data: ELFDATA2LSB64 Type: ET_DYN65Sections:66## Case 1: section has no data.67 - Name: .empty_hash68 Type: SHT_HASH69 Content: ''70## Case 2: section size is less than 2 * 4.71 - Name: .invalid_header72 Type: SHT_HASH73 Content: '00'74## Case 3: nbucket == 1, nchain == 2.75## Section size is less than (2 * nbucket + nchain) * 4.76 - Name: .truncated77 Type: SHT_HASH78 Content: '01000000020000000300000004000000'79## Case 4: nbucket == 1, nchain == 2.80## Section size is greater than (2 * nbucket + nchain) * 4.81 - Name: .oversized82 Type: SHT_HASH83 Content: '0100000002000000030000000400000000'84## Case 5, 6: NChain/NBucket are incorrect and causing 32-bit85## unsigned overflows of intermediate expressions.86 - Name: .overflow187 Type: SHT_HASH88 Bucket: [ ]89 Chain: [ ]90 NBucket: 0x191 NChain: 0xffffffff92 - Name: .overflow293 Type: SHT_HASH94 Bucket: [ ]95 Chain: [ ]96 NBucket: 0xffffffff97 NChain: 0x198 99## Check how we dump the "EntSize" field. When the sh_entsize is 4,100## we don't print it, because it is the default value for the SHT_HASH section.101 102# RUN: yaml2obj --docnum=3 %s -o %t3103# RUN: obj2yaml %t3 | FileCheck %s --check-prefix=ENT-SIZE104 105# ENT-SIZE: - Name: .hash.entsize.0106# ENT-SIZE-NEXT: Type: SHT_HASH107# ENT-SIZE-NEXT: EntSize: 0x0108# ENT-SIZE-NEXT: Content: ''109# ENT-SIZE-NEXT: - Name: .hash.entsize.4.default110# ENT-SIZE-NEXT: Type: SHT_HASH111# ENT-SIZE-NEXT: Content: ''112# ENT-SIZE-NEXT: - Name: .hash.entsize.255113# ENT-SIZE-NEXT: Type: SHT_HASH114# ENT-SIZE-NEXT: EntSize: 0xFF115# ENT-SIZE-NEXT: Content: ''116 117--- !ELF118FileHeader:119 Class: ELFCLASS32120 Data: ELFDATA2LSB121 Type: ET_DYN122Sections:123 - Name: .hash.entsize.0124 Type: SHT_HASH125 EntSize: 0126 Size: 0127 - Name: .hash.entsize.4.default128 Type: SHT_HASH129 EntSize: 4130 Size: 0131 - Name: .hash.entsize.255132 Type: SHT_HASH133 EntSize: 255134 Size: 0135