[llvm-bugs] Issue 9187 in oss-fuzz: llvm/clang-llvm-proto-fuzzer: ASSERT: N->getNumOperands() == 2 && "Update with wrong number of operands"
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Mon Jul 23 00:15:03 PDT 2018
Comment #3 on issue 9187 by ClusterFuzz-External:
llvm/clang-llvm-proto-fuzzer: ASSERT: N->getNumOperands() == 2 && "Update
with wrong number of operands"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=9187#c3
ClusterFuzz has detected this issue as fixed in range
201807110801:201807230239.
Detailed report: https://oss-fuzz.com/testcase?key=5662548375371776
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:
N->getNumOperands() == 2 && "Update with wrong number of operands"
llvm::SelectionDAG::UpdateNodeOperands
DAGCombiner::visitAND
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201806250758:201806260706
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807110801:201807230239
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5662548375371776
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/20180723/0cb578a6/attachment.html>
More information about the llvm-bugs
mailing list