[llvm-bugs] Issue 3659 in oss-fuzz: llvm/clang-fuzzer: ASSERT: BitWidth && "bitwidth too small"

[monor… via monorail via llvm-bugs]

Comment #2 on issue 3659 by  
monor... at clusterfuzz-external.iam.gserviceaccount.com: llvm/clang-fuzzer:  
ASSERT: BitWidth && "bitwidth too small"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3659#c2

ClusterFuzz has detected this issue as fixed in range  
201710210625:201710220448.

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   BitWidth && "bitwidth too small"
   llvm::APSInt::getMaxValue
   AnalyzeImplicitConversions

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710150453:201710160455
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710210625:201710220448

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

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/20171022/0464a0ba/attachment.html>