[llvm-bugs] Issue 10883 in oss-fuzz: llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ in llvm::AArch64RegisterBankInfo::getInstrMapping
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Oct 9 17:05:09 PDT 2018
Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
igm... at gmail.com, eneyman at google.com, llvm-b... at lists.llvm.org,
jfb at chromium.org, v... at apple.com, mitchphi... at outlook.com,
xpl... at gmail.com, akils... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2018-10-10
Type: Bug
New issue 10883 by ClusterFuzz-External:
llvm/llvm-isel-fuzzer--aarch64-gisel: Null-dereference READ in
llvm::AArch64RegisterBankInfo::getInstrMapping
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=10883
Detailed report: https://oss-fuzz.com/testcase?key=5731974405160960
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: 0x000000000010
Crash State:
llvm::AArch64RegisterBankInfo::getInstrMapping
llvm::RegBankSelect::assignInstr
llvm::RegBankSelect::runOnMachineFunction
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201810050224:201810060232
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5731974405160960
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for
more information.
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 need to contact the OSS-Fuzz team with a question, concern, or any
other feedback, 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20181009/882af4a9/attachment-0001.html>
More information about the llvm-bugs
mailing list