Issue 170499
Summary [lldb] crash on invalid input
Labels new issue
Assignees
Reporter google-yfyang
    With a debug build of lldb, it crashes with
```
(lldb) p }u,j<u
WARNING: Logging before InitGoogle() is written to STDERR
F0000 00:00:1764712087.591578 1301326 logging.cc:51] assert.h assertion failed at third_party/llvm/llvm-project/clang/include/clang/Lex/Token.h:193 in IdentifierInfo *clang::Token::getIdentifierInfo() const: !isAnnotation() && "getIdentifierInfo() on an annotation token!"
*** Check failure stack trace: ***
    @     0x55f698b92ab9 absl::log_internal::LogMessage::PrepareToDie()
    @     0x55f698b92067 absl::log_internal::LogMessage::SendToLog()
    @     0x55f698b9201b absl::log_internal::LogMessage::Flush()
    @     0x55f680049605 absl::log_internal::Voidify::operator&&<>()
    @     0x55f698ab60ba __assert_fail
    @     0x55f6882e6250  clang::Token::getIdentifierInfo()
 @     0x55f68a7f479b  clang::Parser::expectIdentifier()
    @ 0x55f68a927aca  clang::Parser::ParseObjCProtocolReferences()
    @ 0x55f68a92e73f  clang::Parser::parseObjCProtocolQualifierType()
    @ 0x55f68a8dbaa1  clang::Parser::ParseDeclarationSpecifiers()
    @ 0x55f68a806558  clang::Parser::ParseDeclarationSpecifiers()
    @ 0x55f68a7fc009  clang::Parser::ParseDeclOrFunctionDefInternal()
    @ 0x55f68a7fb875  clang::Parser::ParseDeclarationOrFunctionDefinition()
    @ 0x55f68a7fae46  clang::Parser::ParseExternalDeclaration()
    @ 0x55f68a7f827d  clang::Parser::ParseTopLevelDecl()
    @     0x55f68a7d8ad6 clang::ParseAST()
    @     0x55f688900f4f lldb_private::ClangExpressionParser::ParseInternal()
    @ 0x55f68890145d  lldb_private::ClangExpressionParser::Parse()
    @ 0x55f688899384  lldb_private::ClangUserExpression::TryParse()
    @ 0x55f688899bd4  lldb_private::ClangUserExpression::Parse()
    @ 0x55f687ec8d59  lldb_private::UserExpression::Evaluate()
    @ 0x55f688b99ffd  lldb_private::Target::EvaluateExpression()
    @ 0x55f687f70463  lldb_private::CommandObjectDWIMPrint::DoExecute()
    @ 0x55f688140480  lldb_private::CommandObjectRaw::Execute()
    @ 0x55f687eddbe2  lldb_private::CommandInterpreter::HandleCommand()
    @ 0x55f687ee3805  lldb_private::CommandInterpreter::IOHandlerInputComplete()
 @     0x55f687ee4009 lldb_private::CommandInterpreter::IOHandlerInputComplete()
    @ 0x55f687d0d536  lldb_private::IOHandlerEditline::Run()
    @ 0x55f687c99892  lldb_private::Debugger::RunIOHandlers()
    @ 0x55f687ee5978  lldb_private::CommandInterpreter::RunCommandInterpreter()
 @     0x55f67fbe00aa  lldb::SBDebugger::RunCommandInterpreter()
    @ 0x55f67fb9a406  Driver::MainLoop()
    @     0x55f67fb9af6a  main
    @ 0x7f6a44e763d4  __libc_start_main
    @     0x55f67fb9602a  _start
PLEASE submit a bug report to go/lldb-crash-bug and include the crash backtrace.
```
You can reproduce this with this invalid input ` p }u,j<u` on a debug build of lldb at HEAD. This is discovered by a fuzzer.
_______________________________________________
llvm-bugs mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/llvm-bugs

Reply via email to