[llvm-bugs] [Bug 26286] New: clang-format will produce temporary file on Windows 10

via llvm-bugs llvm-bugs at lists.llvm.org
Sun Jan 24 22:37:59 PST 2016


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

            Bug ID: 26286
           Summary: clang-format will produce temporary file on Windows 10
           Product: clang
           Version: 3.8
          Hardware: PC
                OS: other
            Status: NEW
          Severity: normal
          Priority: P
         Component: Formatter
          Assignee: unassignedclangbugs at nondot.org
          Reporter: nayuhz at gmail.com
                CC: djasper at google.com, klimek at google.com,
                    llvm-bugs at lists.llvm.org
    Classification: Unclassified

Created attachment 15702
  --> https://llvm.org/bugs/attachment.cgi?id=15702&action=edit
the .clang-format  which can reproduce the bug.

I'am working on Windows 10 x64, and run clang-format 3.8 in cmd.
But I found that clang-format will produce a temporary file when I run:
clang-format.exe -i -style=file file_to_format.c

like Bug 26125, is clang-format not exiting correctly?
but the code have been formatted correctly.

It could be reproduced every times.

On linux, I use clang-format 3.4.2 to do this, but, segmentation fault, as
follow:
Can't find usable .clang-format, using LLVM style
0  libLLVM-3.4.so  0x00007f7d1f28d612 llvm::sys::PrintStackTrace(_IO_FILE*) +
50
1  libLLVM-3.4.so  0x00007f7d1f28d3d4
2  libpthread.so.0 0x00007f7d1df5b130
3  clang-format    0x0000000000bed8a4
4  clang-format    0x0000000000be6d6c
5  clang-format    0x0000000000a30cd7
6  clang-format    0x000000000045da12
7  clang-format    0x000000000045ba54
8  libc.so.6       0x00007f7d1cd57af5 __libc_start_main + 245
9  clang-format    0x000000000045c811
Segmentation fault (core dumped)

The windows version of clang is :
clang version 3.8.0 (trunk)
Target: i686-pc-windows-msvc
Thread model: posix


The attachment is the .clang-format which can reproduce the bug.

-- 
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/20160125/c80a13fb/attachment-0001.html>


More information about the llvm-bugs mailing list