[llvm-bugs] Issue 15711 in oss-fuzz: llvm/clang-fuzzer: Null-dereference READ in clang::LinkageComputer::getLVForDecl
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Mon Jul 8 08:02:52 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 Reproducible Stability-Memory-MemorySanitizer
Engine-libfuzzer OS-Linux Proj-llvm Reported-2019-07-08
Type: Bug
New issue 15711 by ClusterFuzz-External: llvm/clang-fuzzer:
Null-dereference READ in clang::LinkageComputer::getLVForDecl
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=15711
Detailed report: https://oss-fuzz.com/testcase?key=5671959158849536
Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_msan_llvm
Platform Id: linux
Crash Type: Null-dereference READ
Crash Address: 0x000000000000
Crash State:
clang::LinkageComputer::getLVForDecl
clang::NamedDecl::getLinkageInternal
clang::Sema::CheckCompleteVariableDeclaration
Sanitizer: memory (MSAN)
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5671959158849536
Issue filed automatically.
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md 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/20190708/ab19f71f/attachment.html>
More information about the llvm-bugs
mailing list