[llvm-bugs] Issue 12503 in oss-fuzz: llvm/clang-fuzzer:	Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
    ClusterFuzz-External via monorail via llvm-bugs 
    llvm-bugs at lists.llvm.org
       
    Thu Jan 17 07:24:06 PST 2019
    
    
  
Comment #1 on issue 12503 by ClusterFuzz-External: llvm/clang-fuzzer:  
Stack-overflow in clang::FunctionProtoType::getExtProtoInfo
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=12503#c1
ClusterFuzz has detected this issue as fixed in range  
201901160416:201901170409.
Detailed report: https://oss-fuzz.com/testcase?key=5701590395125760
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: 0x7ffe959dfea8
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=201901100404:201901120423
Fixed:  
https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=201901160416:201901170409
Reproducer Testcase:  
https://oss-fuzz.com/download?testcase_id=5701590395125760
See https://github.com/google/oss-fuzz/blob/master/docs/reproducing.md for  
instructions to reproduce this bug locally.
If you suspect that the result above is incorrect, try re-doing that job on  
the test case report page.
-- 
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/20190117/9eabc6cd/attachment-0001.html>
    
    
More information about the llvm-bugs
mailing list