Status: New
Owner: ----
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com, igm...@gmail.com, llvm-b...@lists.llvm.org, v...@apple.com, akils...@apple.com Labels: ClusterFuzz Stability-Memory-AddressSanitizer Unreproducible Engine-libfuzzer Proj-llvm Reported-2018-01-03
Type: Bug

New issue 4908 by ClusterFuzz-External: llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ in llvm::IRMutator::mutateModule
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=4908

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

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

Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
  llvm::IRMutator::mutateModule
  LLVMFuzzerCustomMutator

Sanitizer: address (ASAN)

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

Issue filed automatically.

See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for more information.

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 stable releases.
  * 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 https://github.com/google/oss-fuzz/issues.

--
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.
_______________________________________________
llvm-bugs mailing list
llvm-bugs@lists.llvm.org
http://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to