[LLVMbugs] [Bug 21825] New: [fuzz] Assertion `begin[0] == '\'' && "Invalid token lexed"' failed.

bugzilla-daemon at llvm.org bugzilla-daemon at llvm.org
Wed Dec 10 13:03:46 PST 2014


            Bug ID: 21825
           Summary: [fuzz] Assertion `begin[0] == '\'' && "Invalid token
                    lexed"' failed.
           Product: clang
           Version: trunk
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: -New Bugs
          Assignee: unassignedclangbugs at nondot.org
          Reporter: sami.liedes at iki.fi
                CC: llvmbugs at cs.uiuc.edu
    Classification: Unclassified

Created attachment 13466
  --> http://llvm.org/bugs/attachment.cgi?id=13466&action=edit
test case

Fuzzing discovered that the attached test case, when given as input to

  clang -fno-crash-diagnostics -std=c++11 -xc++ -c -emit-llvm

causes this assertion failure:

invalid-token-lexed.cpp:1:5: error: builtin feature check macro requires a
parenthesized identifier
#if __has_feature('x'
clang-3.6: tools/clang/lib/Lex/LiteralSupport.cpp:1041:
clang::CharLiteralParser::CharLiteralParser(const char *, const char *,
clang::SourceLocation, clang::Preprocessor &, tok::TokenKind): Assertion
`begin[0] == '\'' && "Invalid token lexed"' failed.

You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20141210/a2846f77/attachment.html>

More information about the llvm-bugs mailing list