[llvm-bugs] Issue 9271 in oss-fuzz: llvm/clang-llvm-proto-fuzzer: ASSERT: OS.tell() - Start == FragmentSize && "The stream should advance by fragment size

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #2 on issue 9271 by ClusterFuzz-External:  
llvm/clang-llvm-proto-fuzzer: ASSERT: OS.tell() - Start == FragmentSize  
&& "The stream should advance by fragment size
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9271#c2

ClusterFuzz has detected this issue as fixed in range  
201807261853:201807270312.

Detailed report: https://oss-fuzz.com/testcase?key=4872589737459712

Project: llvm
Fuzzer: libFuzzer_llvm_clang-llvm-proto-fuzzer
Fuzz target binary: clang-llvm-proto-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
   OS.tell() - Start == FragmentSize && "The stream should advance by  
fragment size
   llvm::MCAssembler::writeSectionData
   ELFWriter::writeObject

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807020801:201807030756
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807261853:201807270312

Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=4872589737459712

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
more information.

If you suspect that the result above is incorrect, try re-doing that job on  
the test case report page.

-- 
You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:
https://bugs.chromium.org/hosting/settings

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180727/9044f168/attachment.html>