[llvm-bugs] Issue 44102 in oss-fuzz: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead
ClusterFuzz-External via monorail via llvm-bugs
llvm-bugs at lists.llvm.org
Wed Jan 26 18:54:52 PST 2022
CC: kcc at google.com, mascasa at google.com, jdevl... at apple.com, igm... at gmail.com, davg at google.com, mitchp at google.com, bigch... at gmail.com, eneyman at google.com, llvm-... at lists.llvm.org, jfb at chromium.org, v... at apple.com, mitch... at outlook.com, xpl... at gmail.com, akils... at apple.com
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible Engine-libfuzzer OS-Linux Proj-llvm Reported-2022-01-27
New issue 44102 by ClusterFuzz-External: llvm:clang-fuzzer: Stack-overflow in clang::Preprocessor::PeekAhead
Detailed Report: https://oss-fuzz.com/testcase?key=4685960644788224
Fuzzing Engine: libFuzzer
Fuzz Target: clang-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux
Crash Type: Stack-overflow
Crash Address: 0x7ffc262ceea8
Sanitizer: address (ASAN)
Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=4685960644788224
Issue filed automatically.
See https://google.github.io/oss-fuzz/advanced-topics/reproducing for instructions to reproduce this bug locally.
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. Comments on individual Monorail issues are not monitored.
You received this message because:
1. You were specifically CC'd on the issue
You may adjust your notification preferences at:
Reply to this email to add a comment.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the llvm-bugs