[llvm-bugs] Issue 3764 in oss-fuzz: llvm/clang-fuzzer: ASSERT: ClassDecl->hasFlexibleArrayMember() && "Incomplete array type is not valid"
monor… via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Tue Oct 24 06:12:12 PDT 2017
Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,
llvm-b... at lists.llvm.org, v... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2017-10-24
New issue 3764 by monor... at clusterfuzz-external.iam.gserviceaccount.com:
llvm/clang-fuzzer: ASSERT: ClassDecl->hasFlexibleArrayMember()
&& "Incomplete array type is not valid"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3764
Detailed report: https://oss-fuzz.com/testcase?key=5232567549689856
Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: ASSERT
Crash Address:
Crash State:
ClassDecl->hasFlexibleArrayMember() && "Incomplete array type is not
valid"
clang::Sema::SetCtorInitializers
clang::Sema::ActOnMemInitializers
Sanitizer: address (ASAN)
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5232567549689856
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 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.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20171024/ae4a3781/attachment-0001.html>
More information about the llvm-bugs
mailing list