Open simonvnice opened 1 year ago
Which version of Clang-tidy do you use?
Hi Eugene, Clang-tidy.exe is v15.0.1 (as supplied with Visual Studio 2022 17.6.4)
clang-tidy.exe --version LLVM (http://llvm.org/): LLVM version 15.0.1 Optimized build. Default target: x86_64-pc-windows-msvc Host CPU: tigerlake
@llvm/issue-subscribers-clang-tidy
The issue is generated when check modernize is used. That is, when .clang-tidy contains
Checks:
'
modernize-*
'
Can you try all checks from modernize module to narrow issue to one ?
Hi, I encountered the same crash, I could narrow it down to the check modernize-return-braced-init-list
I'm encountering a similar problem with clang-tidy provided by the newest Microsoft's compiler (17.9.2)
& 'C:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\Llvm\bin\clang-tidy.exe' --version
LLVM (http://llvm.org/):
LLVM version 17.0.3
Optimized build.
For me the problematic setting is modernize-use-nullptr, whereas modernize-return-braced-init-list doesn't cause problems.
I have the same problem as @bgedzior-logi : Exception when checking with hicpp-use-nullptr or modernize-use-nullptr. All other checks work correctly.
clangd --version clangd version 17.0.3 Features: windows Platform: i686-pc-windows-msvc
clang-tidy --version LLVM (http://llvm.org/): LLVM version 17.0.3 Optimized build.
clang --version clang version 17.0.3 Target: i686-pc-windows-msvc Thread model: posix InstalledDir: C:\Program Files\Microsoft Visual Studio\2022\Professional\VC\Tools\Llvm\bin
Since upgrading to Visual Studio Enterprise 17.6.4,
clang-tidy.exe
has started to crash with access violation. Note the STL installed with 17.6.4 requires v15 or greater so an older (working version) cannot be used.Example of crash:
Example of requirement for v15 or greater: