[llvm-bugs] Issue 16899 in oss-fuzz: llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT: Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!"
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Sun Sep 1 05:21:12 PDT 2019
Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
igm... at gmail.com, mitchp at google.com, bigchees... 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 OS-Linux Proj-llvm Reported-2019-09-01
Type: Bug
New issue 16899 by ClusterFuzz-External:
llvm:llvm-opt-fuzzer--x86_64-instcombine: ASSERT:
Amt->getType()->isIntegerTy() && "Allocation array size is not an integer!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=16899
Detailed Report: https://oss-fuzz.com/testcase?key=5740721801265152
Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: llvm-opt-fuzzer--x86_64-instcombine
Job Type: libfuzzer_msan_llvm
Platform Id: linux
Crash Type: ASSERT
Crash Address:
Crash State:
Amt->getType()->isIntegerTy() && "Allocation array size is not an
integer!"
llvm::AllocaInst::AllocaInst
BitcodeReader::parseFunctionBody
Sanitizer: memory (MSAN)
Crash Revision:
https://oss-fuzz.com/revisions?job=libfuzzer_msan_llvm&revision=201906300300
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5740721801265152
Issue filed automatically.
See https://google.github.io/oss-fuzz/advanced-topics/reproducing for
instructions to reproduce this bug locally.
--
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/20190901/6006a033/attachment.html>
More information about the llvm-bugs
mailing list