[llvm-bugs] Issue 6051 in oss-fuzz: llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: ArgIdx == 2 && "Invalid argument index"

[ClusterFuzz-External via monorail via llvm-bugs]

Comment #5 on issue 6051 by ClusterFuzz-External:  
llvm/llvm-opt-fuzzer--x86_64-gvn: ASSERT: ArgIdx == 2 && "Invalid argument  
index"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=6051#c5

ClusterFuzz has detected this issue as fixed in range  
201808160456:201808170407.

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

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

Crash Type: ASSERT
Crash Address:
Crash State:
   ArgIdx == 2 && "Invalid argument index"
   llvm::MemoryLocation::getForArgument
   llvm::AAResults::getModRefInfo

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201802050757:201802060728
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201808160456:201808170407

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

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/20180817/18c2c5cf/attachment-0001.html>