[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 --- Comment #5 from Igor Kushnir --- Please reply under the original bug, not its duplicates. The reporters of duplicate bugs are automatically subscribed to the original bug. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 JATothrim changed: What|Removed |Added CC||jarmo.tii...@gmail.com --- Comment #4 from JATothrim --- @Staffan Palmroos If it is of any help, I think there is a way to avoid crashing when typing a #include. Write the line somewhere else, and pasting the complete line in one go may avoid the crash. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 --- Comment #3 from Staffan Palmroos --- Ok, thanks! I have now got crashes in other situations than what I first described, i.e. adding an #include after hibernation. Hibernation likely has nothing to do with it. I did a cursory check on the clang github before but I didn't find anything that directly caught my eye. -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=486932| -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Igor Kushnir --- (In reply to Igor Kushnir from comment #1) > Steps to reproduce this crash are very similar to those of Bug 486932. The > backtrace is different. But both bugs affect Clang 17 and probably not > earlier Clang versions. Actually the backtrace matches the backtrace in the description of Bug 486932 plus debug symbols, but not the backtrace I posted in a comment there. So this *is* a duplicate. *** This bug has been marked as a duplicate of bug 486932 *** -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=486932 -- You are receiving this mail because: You are watching all bug changes.
[kdevelop] [Bug 487378] Crash when adding #include statement
https://bugs.kde.org/show_bug.cgi?id=487378 Igor Kushnir changed: What|Removed |Added CC||igor...@gmail.com --- Comment #1 from Igor Kushnir --- Steps to reproduce this crash are very similar to those of Bug 486932. The backtrace is different. But both bugs affect Clang 17 and probably not earlier Clang versions. I suggest trying to search for includes/headers, crashes and parts of the backtraces at https://github.com/llvm/llvm-project/ . It is likely that someone has already fixed the bug in the main LLVM branch. Then the fix can be backported to Clang 17 by distros. -- You are receiving this mail because: You are watching all bug changes.
