[llvm-bugs] Issue 13244 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in new map?"

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #2 on issue 13244 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-earlycse: ASSERT: !FoundVal && "Key already in  
new map?"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13244#c2

ClusterFuzz has detected this issue as fixed in range  
201902280430:201903010424.

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

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:
   !FoundVal && "Key already in new map?"
   llvm::DenseMapBase<llvm::DenseMap<SimpleValue,  
llvm::ScopedHashTableVal<SimpleVa
   llvm::DenseMapBase<llvm::DenseMap<SimpleValue,  
llvm::ScopedHashTableVal<SimpleVa

Sanitizer: address (ASAN)

Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902280430:201903010424

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

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.

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/20190301/f397600d/attachment.html>