[llvm-bugs] Issue 7424 in oss-fuzz: llvm/clang-fuzzer:	Stack-overflow in clang::DiagnosticIDs::isUnrecoverable
    ClusterFuzz-External via monorail via llvm-bugs 
    llvm-bugs at lists.llvm.org
       
    Thu Apr  5 20:31:59 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, 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-04-06
Type: Bug
New issue 7424 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow  
in clang::DiagnosticIDs::isUnrecoverable
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=7424
Detailed report: https://oss-fuzz.com/testcase?key=6032465157160960
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: 0x7ffd6f9d3e78
Crash State:
   clang::DiagnosticIDs::isUnrecoverable
   clang::DiagnosticIDs::ProcessDiag
   clang::DiagnosticsEngine::EmitCurrentDiagnostic
Sanitizer: address (ASAN)
Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=6032465157160960
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/20180405/8a1f6bc0/attachment-0001.html>
    
    
More information about the llvm-bugs
mailing list