[llvm-bugs] Issue 45102 in oss-fuzz: llvm:clangd-fuzzer: ASSERT: !isAnnotation() && "getIdentifierInfo() on an annotation token!"

[ClusterFuzz-External via monorail via llvm-bugs]

Status: New
Owner: ----
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-02-27
Type: Bug

New issue 45102 by ClusterFuzz-External: llvm:clangd-fuzzer: ASSERT: !isAnnotation() && "getIdentifierInfo() on an annotation token!"
https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=45102

Detailed Report: https://oss-fuzz.com/testcase?key=6285015980310528

Project: llvm
Fuzzing Engine: libFuzzer
Fuzz Target: clangd-fuzzer
Job Type: libfuzzer_asan_llvm
Platform Id: linux

Crash Type: ASSERT
Crash Address: 
Crash State:
  !isAnnotation() && "getIdentifierInfo() on an annotation token!"
  clang::Token::getIdentifierInfo
  clang::Parser::expectIdentifier
  
Sanitizer: address (ASAN)

Regressed: https://oss-fuzz.com/revisions?job=libfuzzer_asan_llvm&range=202101130625:202101140605

Reproducer Testcase: https://oss-fuzz.com/download?testcase_id=6285015980310528

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:
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/20220227/55678df5/attachment.html>