[llvm-bugs] Issue 8008 in oss-fuzz: llvm/clang-fuzzer: Stack-overflow in Evaluate
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Wed Apr 25 02:13:11 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-25
Type: Bug
New issue 8008 by ClusterFuzz-External: llvm/clang-fuzzer: Stack-overflow
in Evaluate
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=8008
Detailed report: https://oss-fuzz.com/testcase?key=5561985295974400
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: 0x7fff56685800
Crash State:
Evaluate
FloatExprEvaluator::VisitBinaryOperator
clang::StmtVisitorBase<clang::make_const_ptr, FloatExprEvaluator,
bool>::Visit
Sanitizer: address (ASAN)
Reproducer Testcase:
https://oss-fuzz.com/download?testcase_id=5561985295974400
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
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/20180425/d2b218e6/attachment.html>
More information about the llvm-bugs
mailing list