[llvm-bugs] Issue 3351 in oss-fuzz: llvm: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo

[monor… via monorail via llvm-bugs]

Status: New
Owner: ----
CC: kcc at google.com,  mascasa at google.com,  jdevlieg... at apple.com,   
llvm-b... at lists.llvm.org
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible  
Engine-libfuzzer Proj-llvm Reported-2017-09-10

New issue 3351 by monor... at clusterfuzz-external.iam.gserviceaccount.com:  
llvm: Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3351

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

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Fuzz target binary: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffc7b0d8ca8
Crash State:
   clang::FunctionProtoType::getExtProtoInfo
   clang::FunctionProtoType::Profile
   llvm::ContextualFoldingSet<clang::FunctionProtoType,  
clang::ASTContext&>::NodeEq

Sanitizer: address (ASAN)

Regressed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201709010452:201709040449

Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5418646333554688

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/20170910/3949a22e/attachment.html>