search

llvm / llvm-project

The LLVM Project is a collection of modular and reusable compiler and toolchain technologies.
http://llvm.org
Other
28.53k stars 11.79k forks source link

Crash on QT Project #110493

Open cyko69 opened 2 weeks ago

cyko69 commented 2 weeks ago

Hi, sadly I cannot provide the code. It's a QT 6.7.2 CMake project.

I stumbled upon this while figuring out why -internal-isystem "C:\Qt\Tools\llvm-mingw1706_64\include\c++\" does not include "C:\Qt\Tools\llvm-mingw1706_64\include\c++\v1"

I still don't know but maybe it has to do with it...

Stack dump:
0.      Program arguments: clangd --check=pendingchangeshandler.cpp
Exception Code: 0xC0000005
0x00007FF7273C0000, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x0 byte(s)
0x00007FF7275130BB, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x1530BB byte(s)
0x00007FF72751273C, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x15273C byte(s)
0x00007FF727503C88, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x143C88 byte(s)
0x00007FF7283CD5CB, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x100D5CB byte(s)
0x00007FF728362305, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0xFA2305 byte(s)
0x00007FF72835FE81, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0xF9FE81 byte(s)
0x00007FF7283569ED, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0xF969ED byte(s)
0x00007FF72B587A0C, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x41C7A0C byte(s)
0x00007FFA84F27374, C:\Windows\System32\KERNEL32.DLL(0x00007FFA84F10000) + 0x17374 byte(s), BaseThreadInitThunk() + 0x14 byte(s)
0x00007FFA862DCC91, C:\Windows\SYSTEM32\ntdll.dll(0x00007FFA86290000) + 0x4CC91 byte(s), RtlUserThreadStart() + 0x21 byte(s)
llvmbot commented 2 weeks ago

@llvm/issue-subscribers-clangd

Author: None (cyko69)

Hi, sadly I cannot provide the code. It's a QT 6.7.2 CMake project. I stumbled upon this while figuring out why -internal-isystem "C:\\Qt\\Tools\\llvm-mingw1706_64\\include\\c++\\" does not include "C:\\Qt\\Tools\\llvm-mingw1706_64\\include\\c++\\v1" I still don't know but maybe it has to do with it... ``` Stack dump: 0. Program arguments: clangd --check=pendingchangeshandler.cpp Exception Code: 0xC0000005 0x00007FF7273C0000, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x0 byte(s) 0x00007FF7275130BB, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x1530BB byte(s) 0x00007FF72751273C, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x15273C byte(s) 0x00007FF727503C88, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x143C88 byte(s) 0x00007FF7283CD5CB, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x100D5CB byte(s) 0x00007FF728362305, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0xFA2305 byte(s) 0x00007FF72835FE81, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0xF9FE81 byte(s) 0x00007FF7283569ED, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0xF969ED byte(s) 0x00007FF72B587A0C, C:\clangd_19.1.0\bin\clangd.exe(0x00007FF7273C0000) + 0x41C7A0C byte(s) 0x00007FFA84F27374, C:\Windows\System32\KERNEL32.DLL(0x00007FFA84F10000) + 0x17374 byte(s), BaseThreadInitThunk() + 0x14 byte(s) 0x00007FFA862DCC91, C:\Windows\SYSTEM32\ntdll.dll(0x00007FFA86290000) + 0x4CC91 byte(s), RtlUserThreadStart() + 0x21 byte(s) ```
HighCommander4 commented 2 weeks ago

Could you have a look at https://clangd.llvm.org/troubleshooting#getting-stacktraces-from-crashes and see if you can get a symbolized stack trace?

cyko69 commented 2 weeks ago

With llvm-symbolizer in path, my stand alone version of clangd doesnt resolve its symbols. (Or do I have to do more than just put it in my path?) The clangd version installed with llvm does not have this issue.

llvm: I[16:12:54.553] clangd version 19.1.0 I[16:12:54.554] Features: windows

stand alone: I[16:12:40.532] clangd version 19.1.0 (https://github.com/llvm/llvm-project a4bf6cd7cfb1a1421ba92bca9d017b49936c55e4) I[16:12:40.534] Features: windows+grpc

HighCommander4 commented 2 weeks ago

The clangd version installed with llvm does not have this issue.

Could you get a stack trace with that version then?

cyko69 commented 2 weeks ago

I dont know how to force a stacktrace with that version.

HighCommander4 commented 2 weeks ago

I dont know how to force a stacktrace with that version.

Do you mean that version doesn't crash? Or it crashes but doesn't print a stack trace?

cyko69 commented 2 weeks ago

Sorry, I mean the llvm installed version does not crash.

Am 3. Oktober 2024 02:01:07 MESZ schrieb Nathan Ridge @.***>:

I dont know how to force a stacktrace with that version.

Do you mean that version doesn't crash? Or it crashes but doesn't print a stack trace?

HighCommander4 commented 1 week ago

Thanks.

In the absence of a reproducer or stack trace, we don't have anything to go on to investigate this crash further.

However, it seems like you at least have a workaround: use the version that doesn't crash.