[llvm-bugs] [Bug 28381] New: Windows: Crash with absolute path with forward slashes (at reparse, with CXTranslationUnit_PrecompiledPreamble)

[via llvm-bugs]

https://llvm.org/bugs/show_bug.cgi?id=28381

            Bug ID: 28381
           Summary: Windows: Crash with absolute path with forward slashes
                    (at reparse, with
                    CXTranslationUnit_PrecompiledPreamble)
           Product: clang
           Version: 3.8
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: libclang
          Assignee: unassignedclangbugs at nondot.org
          Reporter: nikolai.kosjar at qt.io
                CC: klimek at google.com, llvm-bugs at lists.llvm.org
    Classification: Unclassified

Created attachment 16670
  --> https://llvm.org/bugs/attachment.cgi?id=16670&action=edit
libclang calls to reproduce, test sources to trigger the bug, stackstrace

See attachment crashForwardSlashes.zip
 - libclangclient.cpp: Compile this to re-produce.
 - testsources: main.cpp includes empty.h
 - stacktrace.txt at crash/assert

Consider the invocations:
 1) libclangclient.exe D:\absolute\path\to\main.cpp
    ==> fine
 2) libclangclient.exe D:/absolute/path/to/main.cpp
    ==> crash

It will crash obviously with a message box for a debug build of llvm (assert).

For a release mode build it does not crash for the given example, but in a
real world application making more libclang calls it will crash at some later
point in time.

-- 
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/20160701/66b23993/attachment.html>