Updates:
Labels: ClusterFuzz-Verified
Status: Verified
Comment #5 on issue 3450 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow
in clang::format::TokenAnnotator::annotate
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3450#c5
ClusterFuzz
Comment #4 on issue 3450 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow
in clang::format::TokenAnnotator::annotate
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3450#c4
ClusterFuzz has detected this issue as fixed in range
201710121744:201710130152.
Updates:
Cc: v...@apple.com
Comment #3 on issue 3450 by
monor...@clusterfuzz-external.iam.gserviceaccount.com: llvm: Stack-overflow
in clang::format::TokenAnnotator::annotate
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3450#c3
(No comment was entered for this change.)
--
Comment #2 on issue 3450 by k...@google.com: llvm: Stack-overflow in
clang::format::TokenAnnotator::annotate
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3450#c2
henri@, these bugs are automatically filed only here, we do not have any
mechanism to report them to LLVM's bugzilla.
Al
Comment #1 on issue 3450 by he...@nerv.fi: llvm: Stack-overflow in
clang::format::TokenAnnotator::annotate
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=3450#c1
Where was this automatically filed in upstream or does that mean this issue
report? If it was automatically reported to up
Status: New
Owner:
CC: k...@google.com, masc...@google.com, jdevlieg...@apple.com,
llvm-b...@lists.llvm.org
Labels: ClusterFuzz Stability-Memory-AddressSanitizer Reproducible
Engine-libfuzzer Proj-llvm Reported-2017-09-21
New issue 3450 by monor...@clusterfuzz-external.iam.gserviceac
