[llvm-bugs] Issue 5044 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N->getNodeId() == -1 && "Node already inserted!"

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #6 on issue 5044 by ClusterFuzz-External:  
llvm/llvm-isel-fuzzer--x86_64-O2: ASSERT: N->getNodeId() == -1 && "Node  
already inserted!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5044#c6

ClusterFuzz has detected this issue as fixed in range  
201807110801:201807230239.

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   N->getNodeId() == -1 && "Node already inserted!"
   ScheduleDAGRRList::PickNodeToScheduleBottomUp
   ScheduleDAGRRList::Schedule

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201710160455:201710190451
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201807110801:201807230239

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

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/1e25e25f/attachment.html>