Summary: | crash in clang_Cursor_getParsedComment | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Cyrille Dunant <cyrille.dunant> |
Component: | Language Support: CPP (Clang-based) | Assignee: | kdevelop-bugs-null |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | cpigat242, simonandric5 |
Priority: | VHI | ||
Version: | 4.90.90 | ||
Target Milestone: | 5.0.0 | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | https://commits.kde.org/kdevelop/a2712c8d9691375545f502c10f4f76fa10452e90 | Version Fixed In: | 5.2.1 |
Description
Cyrille Dunant
2016-01-19 11:45:49 UTC
just saw that myself, twice in a row. Also possibly related: https://llvm.org/bugs/show_bug.cgi?id=24280 We really need to find a reproducible testcase for this. Hey Cyrille, do you always get this crash with your project? If so, is it an open source project so that I can to reproduce it myself? Otherwise, could you try to figure out what file is triggering this crash and we figure out a minimal testcase from there? I think it would help to add debug output before we call clang_Cursor_getParsedComment to see what file/cursor is triggering the crash. Without a way to reproduce this, we and upstream are at a loss at improving this situation, I'm afraid. It is an opensource project, but not released. I am completely fine giving you a version However, the latest kdevelop snapshot from opensuse does not crash... Which is good, perhaps. If you still want a copy of my project, I'll send it to you tomorrow. @Cyrille: Still the same Clang version? this must be fixed upstream, and we need a reproducible way to trigger this. if you have one that takes down kdevelop, please show it here and I'll create a test out of it for upstream Git commit a2712c8d9691375545f502c10f4f76fa10452e90 by Sven Brauch. Committed on 17/11/2017 at 00:45. Pushed by brauch into branch '5.2'. work around clang bug 35333: don't crash when switching git branches See https://bugs.llvm.org/show_bug.cgi?id=35333 for details and explanation. We need to do two things to work around this bug: disable -Wdocumentation, and only use the plain text from the comments instead of the parsed version. REVIEW: https://phabricator.kde.org/D8857 Related: bug 372686 FIXED-IN: 5.2.1 M +4 -0 plugins/clang/duchain/builder.cpp M +7 -0 plugins/clang/duchain/parsesession.cpp https://commits.kde.org/kdevelop/a2712c8d9691375545f502c10f4f76fa10452e90 |