[llvm-bugs] Issue 3974 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-O2: Null-dereference READ in llvm::IRMutator::mutateModule
monor… via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Oct 31 23:06:56 PDT 2017
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
llvm-b... at lists.llvm.org, v... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Unreproducible
Engine-libfuzzer Proj-llvm Reported-2017-11-01
New issue 3974 by monor... at clusterfuzz-external.iam.gserviceaccount.com:
llvm/llvm-isel-fuzzer--aarch64-O2: Null-dereference READ in
Detailed report: https://oss-fuzz.com/testcase?key=5289625049366528
Fuzz target binary: llvm-isel-fuzzer--aarch64-O2
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Sanitizer: address (ASAN)
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
Note: This crash might not be reproducible with the provided testcase. That
said, for the past 14 days we've been seeing this crash frequently. If you
are unable to reproduce this, please try a speculative fix based on the
crash stacktrace in the report. The fix can be verified by looking at the
crash statistics in the report, a day after the fix is deployed. We will
auto-close the bug if the crash is not seen for 14 days.
When you fix this bug, please
* mention the fix revision(s).
* state whether the bug was a short-lived regression or an old bug in any
* add any other useful information.
This information can help downstream consumers.
If you have questions for the OSS-Fuzz team, please file an issue at
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-bugs