Created attachment 189213 [details] Backtrace from running kdevelop from inside of gdb *** Immediately after typing "std::array" at the beginning of a (not otherwise empty) line, kdevelop crashes with a segmentation fault. Dr. Konqi is unable to produce a backtrace of the crash for some reason as described here: https://discuss.kde.org/t/dr-konqi-cannot-load-a-backtrace-after-kdevelop-crashes/43991 but I ran kdevelop from within gdb to get a backtrace anyway. *** SUMMARY STEPS TO REPRODUCE 1. Have a very short test C++ project with a main.cpp that #includes <array> 2. Have a line in there reading "uint32_t random_bytes_buffer[buffer_size];" 3. Try to change the C style array to a C++ style std::array<uint32_t, 4>, beginning by deleting the "uint32_t" keyword and replacing it with "std::array". OBSERVED RESULT Kdevelop crashes. EXPECTED RESULT Kdevelop should not crash. SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 6.5.5 KDE Frameworks Version: 6.22.0 Qt Version: 6.10.1 LLVM: 21.1.8 ADDITIONAL INFORMATION Note: The crash seems to happen deep inside of LLVM code. It may actually be a bug in LLVM instead of kdevelop itself.
BTW, the project in question is extremely simple and short and not sensitive at all. I can post the whole thing if that's helpful.
Forgot to mention: The crash is 100% reproducible for me at the moment.
When removing the [buffer_size] at the end of the variable name first, I can change the uint32_t to std::array<uint32_t, buffer_size> without a crash.