[llvm-bugs] Issue 13204 in oss-fuzz: llvm/llvm-isel-fuzzer--x86_64-O2: Null-dereference READ in MachineCSE::ProcessBlock
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Wed Mar 13 07:30:44 PDT 2019
Comment #2 on issue 13204 by ClusterFuzz-External:
llvm/llvm-isel-fuzzer--x86_64-O2: Null-dereference READ in
MachineCSE::ProcessBlock
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=13204#c2
ClusterFuzz has detected this issue as fixed in range
201903110335:201903120333.
Detailed report: https://oss-fuzz.com/testcase?key=5756498557272064
Project: llvm
Fuzzer: libFuzzer_llvm_llvm-isel-fuzzer--x86_64-O2
Fuzz target binary: llvm-isel-fuzzer--x86_64-O2
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Null-dereference READ
Crash Address: 0x000000000010
Crash State:
MachineCSE::ProcessBlock
MachineCSE::runOnMachineFunction
llvm::MachineFunctionPass::runOnFunction
Sanitizer: address (ASAN)
Regressed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201902180416:201902190429
Fixed:
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201903110335:201903120333
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5756498557272064
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/20190313/fbe94fb4/attachment.html>
More information about the llvm-bugs
mailing list