Displaying 2 results from an estimated 2 matches for "parsesection".
Did you mean:
parse_section
2017 Aug 29
3
how to auto-report LLVM bugs found by fuzzing?
...issues/detail?id=3216&q=label%3AProj-llvm%20dwarfdump-fuzzer&colspec=ID%20Type%20Component%20Status%20Proj%20Reported%20Owner%20Summary
Crash Type: ASSERT
Crash Address:
Crash State:
result <= UINT32_MAX
llvm::object::WasmObjectFile::parseStartSection
llvm::object::WasmObjectFile::parseSection
Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x60200000009a
Crash State:
llvm::object::WasmObjectFile::parseCustomSection
llvm::object::WasmObjectFile::parseSection
llvm::object::WasmObjectFile::WasmObjectFile
Crash Type: Heap-buffer-overflow READ 1
Crash Address: 0x604000000776
C...
2017 Aug 29
2
how to auto-report LLVM bugs found by fuzzing?
...c=ID%
> 20Type%20Component%20Status%20Proj%20Reported%20Owner%20Summary
> >
> > Crash Type: ASSERT
> > Crash Address:
> > Crash State:
> > result <= UINT32_MAX
> > llvm::object::WasmObjectFile::parseStartSection
> > llvm::object::WasmObjectFile::parseSection
> >
> > Crash Type: Heap-buffer-overflow READ 1
> > Crash Address: 0x60200000009a
> > Crash State:
> > llvm::object::WasmObjectFile::parseCustomSection
> > llvm::object::WasmObjectFile::parseSection
> > llvm::object::WasmObjectFile::WasmObjectFile
>...