[llvm-bugs] Issue 5734 in oss-fuzz: llvm: Stack-overflow in clang::Sema::GetNameFromUnqualifiedId

[ClusterFuzz-External via monorail via llvm-bugs]

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, 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-01-27
Type: Bug

New issue 5734 by ClusterFuzz-External: llvm: Stack-overflow in  
clang::Sema::GetNameFromUnqualifiedId
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=5734

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

Project: llvm
Fuzzer: libFuzzer_llvm_clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: Stack-overflow
Crash Address: 0x7ffdfd22dc98
Crash State:
   clang::Sema::GetNameFromUnqualifiedId
   clang::Sema::DecomposeUnqualifiedId
   clang::Sema::ActOnIdExpression

Sanitizer: address (ASAN)

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

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

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/20180126/4dfe1a25/attachment-0001.html>