Comment #2 on issue 6033 by ClusterFuzz-External: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: loBit <= BitWidth && "loBit out of range"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6033#c2

ClusterFuzz has detected this issue as fixed in range 201802080701:201802090558.

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

Project: llvm
Fuzzer: libFuzzer_llvm_llvm-opt-fuzzer--x86_64-earlycse
Fuzz target binary: llvm-opt-fuzzer--x86_64-earlycse
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address:
Crash State:
  loBit <= BitWidth && "loBit out of range"
  llvm::APInt::setBits
  computeKnownBitsFromAssume

Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201801240651:201801250632 Fixed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802080701:201802090558

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

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.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to