[llvm-bugs] Issue 9221 in oss-fuzz: llvm/clang-fuzzer: ASSERT: SubExpr->getType()->isIntegerType() && "Unexpected imaginary literal."

ClusterFuzz-External via monorail via llvm-bugs llvm-bugs at lists.llvm.org
Sun Jul 1 21:43:30 PDT 2018

Status: New
Owner: ----
CC: kcc at google.com, mascasa at google.com, jdevlieg... at apple.com,  
igm... at gmail.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-07-02
Type: Bug

New issue 9221 by ClusterFuzz-External: llvm/clang-fuzzer: ASSERT:  
SubExpr->getType()->isIntegerType() && "Unexpected imaginary literal."

Detailed report: https://oss-fuzz.com/testcase?key=5984739172286464

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:
   SubExpr->getType()->isIntegerType() && "Unexpected imaginary literal."
   clang::StmtVisitorBase<clang::make_const_ptr, ComplexExprEvaluator,  

Sanitizer: address (ASAN)


Reproducer Testcase:  

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  

You received this message because:
   1. You were specifically CC'd on the issue

You may adjust your notification preferences at:

Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180701/f65b8963/attachment.html>

More information about the llvm-bugs mailing list