[llvm-bugs] [Bug 47604] New: Assertion failed: Index >= End && "Unexpected parser error."

via llvm-bugs llvm-bugs at lists.llvm.org
Mon Sep 21 11:52:14 PDT 2020


            Bug ID: 47604
           Summary: Assertion failed: Index >= End && "Unexpected parser
           Product: libraries
           Version: trunk
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P
         Component: Support Libraries
          Assignee: unassignedbugs at nondot.org
          Reporter: drivehappy at gmail.com
                CC: llvm-bugs at lists.llvm.org

Created attachment 23990
  --> https://bugs.llvm.org/attachment.cgi?id=23990&action=edit
Response file that contains '-Xclang' argument.

The following assertion is firing when running clang-cl under Windows with a
response file that includes '-Xclang' arguments.

    Assertion failed: Index >= End && "Unexpected parser error.", file
C:\src\llvm_package_6923b0a7\llvm-project\llvm\lib\Option\OptTable.cpp, line
    PLEASE submit a bug report to https://bugs.llvm.org/ and include the crash
backtrace, preprocessed source, and associated run script.
    Stack dump:
    0.      Program arguments: clang-cl @test.rsp
     #0 0x00007ff774a4e716 C:\Program Files\LLVM\bin\clang-cl.exe 0x212e716
(C:\Program Files\LLVM\bin\clang-cl.exe+0x212e716)
     #1 0x00007ff774a4e716
     #2 0x00007ff774a4e716 (C:\Program Files\LLVM\bin\clang-cl.exe+0x212e716)
     #3 0x00007ffa13801891 (C:\WINDOWS\System32\ucrtbase.dll+0x71891)
     #4 0x00007ffa13802861 (C:\WINDOWS\System32\ucrtbase.dll+0x72861)
     #5 0x00007ffa1380427e (C:\WINDOWS\System32\ucrtbase.dll+0x7427e)
     #6 0x00007ffa13804175 C:\Program Files\LLVM\bin\clang-cl.exe 0x1eb1372
C:\Program Files\LLVM\bin\clang-cl.exe 0x347d
     #7 0x00007ffa13804175 C:\Program Files\LLVM\bin\clang-cl.exe 0x4c7cfa0
     #8 0x00007ffa13804175
     #9 0x00007ffa13804175 (C:\WINDOWS\System32\ucrtbase.dll+0x74175)
    0x00007FF774A4E716 (0x0000C338C19A312B 0x000000389318E270
0x0000000000000016 0x00007FF774A4E710)
    0x00007FFA13801891 (0x0000000000000001 0x00007FF700000000
0x0000000000000000 0x000000389318E240), raise() + 0x1E1 bytes(s)
    0x00007FFA13802861 (0x0002000000000003 0x0000022C00000003
0x00007FFA1385DE60 0x00007FF778F38C24), abort() + 0x31 bytes(s)
    0x00007FFA1380427E (0x0000022CCF753490 0x00007FF7747D4701
0x0000022CCF7A6BA0 0x00000000000001E2), _get_wpgmptr() + 0x195E bytes(s)
    0x00007FFA13804175 (0x00000000000001E2 0x00007FF778F38C24
0x0000000000000002 0x00000000000000A3), _get_wpgmptr() + 0x1855 bytes(s)
    0x00007FFA13804501 (0x00007FF7775A0F00 0x00007FF7775A13A2
0x000000389318EDE0 0x00007FF7775A0F00), _wassert() + 0x71 bytes(s)
    0x00007FF7747D1372 (0x000000000000006B 0x0000000000000000
0x0000022CCF72A160 0x0000022CCF72A150)
    0x00007FF77292347D (0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000)
    0x00007FF77759CFA0 (0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000)
    0x00007FFA14EA6FD4 (0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000), BaseThreadInitThunk() + 0x14 bytes(s)
    0x00007FFA1587CEC1 (0x0000000000000000 0x0000000000000000
0x0000000000000000 0x0000000000000000), RtlUserThreadStart() + 0x21 bytes(s)

I suspect this was caused by a recent refactoring change:

Note: There appears there is a comment referring a FIXME for "@" support,
unknown if it's related:

This occurred running Clang version 12.0 from the Windows snapshot build
provided from here: http://llvm.org/builds/ (built against commit 6923b0a7 - 28
Aug 2020)

I've attached a slimmed down response file that produces the assertion, which
can be run: `clang-cl @test.rsp` (this points to building sqlite3.c, however it
appears the source file present on the filesystem isn't necessary to trigger
the assertion).

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/20200921/e059ed34/attachment.html>

More information about the llvm-bugs mailing list