[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2023-01-02 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #18 from Igor Kushnir --- (In reply to Igor Kushnir from comment #17) > The line in KDevelop code where the crash occurs (cmakelistsparser.cpp:180): > func.arguments << CMakeFunctionArgument( > QString::fromLocal8Bit(token->text,

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2023-01-01 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #17 from Igor Kushnir --- (In reply to Eugene Shalygin from comment #12) > Got back to this after some time. Seems like KDevelop's CMake parser can't > handle strings with 0 bytes inside. Specifically, creating the CMake console > project

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2022-07-08 Thread Gabriele Menna
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #16 from Gabriele Menna --- I agree. The test case attached to Bug 455533 features duplicated test_case, as in the project causing the crash on my setup. Only, the crash is totally reproducible, contrary to what stated in the related bug

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2022-07-07 Thread Igor Kushnir
https://bugs.kde.org/show_bug.cgi?id=439592 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #15 from Igor

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2022-07-07 Thread Gabriele Menna
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #14 from Gabriele Menna --- NOTE: the above stack trace was caused by a duplicated add_test() cmake command, located in two different CMakeLists.txt. After the duplication was removed, the crash is no more occuring. -- You are receiving

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2022-07-07 Thread Gabriele Menna
https://bugs.kde.org/show_bug.cgi?id=439592 Gabriele Menna changed: What|Removed |Added CC||gab...@gmail.com --- Comment #13 from

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2022-04-08 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #12 from Eugene Shalygin --- Got back to this after some time. Seems like KDevelop's CMake parser can't handle strings with 0 bytes inside. Specifically, creating the CMake console project from the template and appending contents of

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-08-03 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #11 from Eugene Shalygin --- Removing "0"s from that file allows KDevelop to finish project parsing without crashing. -- You are receiving this mail because: You are watching all bug changes.

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-08-03 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #10 from Eugene Shalygin --- Debug build crashes as well with the same backtrace as in the OP. 1. rm -fr ~/.cache/kdevduchain 2. open the cmake project and wait It crashes and at that moment the parsing progress shows

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-31 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #9 from Eugene Shalygin --- Yes, and sometimes when it asks for it after a crash too. Can't say either choice (to clean or not to clean) is more likely leads to a crash. -- You are receiving this mail because: You are watching all bug

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-30 Thread Sven Brauch
https://bugs.kde.org/show_bug.cgi?id=439592 Sven Brauch changed: What|Removed |Added CC||m...@svenbrauch.de --- Comment #8 from Sven

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-30 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 Eugene Shalygin changed: What|Removed |Added Status|RESOLVED|REOPENED Ever confirmed|0

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-23 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 Eugene Shalygin changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-22 Thread Bug Janitor Service
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-08 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=439592 Milian Wolff changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-07 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #3 from Eugene Shalygin --- Debug build does not seem to crash. In console output I see the following: kdevelop.plugins.definesandincludes: error while fetching defines for the compiler: "clang" ("-xc", "-std=c++17", "-dM", "-E", "-")

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-07 Thread Eugene Shalygin
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #2 from Eugene Shalygin --- Unfortunately, under Valgrind C++ parsing does not work at all: KDevelop can not find any include file even those from C++ stdlib. I see many messages from Valgring with the following content: Thread 1: status =

[kdevelop] [Bug 439592] KDevelop always crashes when parsing the CMake project

2021-07-07 Thread Milian Wolff
https://bugs.kde.org/show_bug.cgi?id=439592 --- Comment #1 from Milian Wolff --- that looks pretty odd as it doesn't hint at anything from kdevelop directly can you please try to reproduce this with valgrind and show the report here then? -- You are receiving this mail because: You are