https://bugs.kde.org/show_bug.cgi?id=486932
--- Comment #2 from JATothrim <jarmo.tii...@gmail.com> --- > I don't find anything like this backtrace in my local collection. Could be a > libclang 17 regression (I am still at v16). Well, good then that I opened a bug report for this. I have had KDevelop crashing this way for about a month, and the backtrace is from KDevelop's project (via GDB). I have seen it crash even before completing "#include". > Yes, please use `options=(!strip)` and `-DCMAKE_BUILD_TYPE=RelWithDebInfo`. I think I'll rebuild just to re-produce the bt and try print the locals just before descending into clang code. However, clang would be painful to build in this mode.. last time I did it the install directory was +10GiB o__O I did have an idea for parser blacklist: if the text line is found from it, the code completion would not be triggered until the typed text is longer than best matching black list entry. This could perhaps allow the user (temporally) dealing with cases where the parser might crash on incomplete code, or just being too annoying. For example, it doesn't make sense to start trying to suggest anything at "#include " for me, as the next two characters would greatly shrink the possibilities, and even suggesting anything at "#include <" is kind of just irritating. I know an such blacklist entry would prevent completing the "#include" keyword, but I would like to suppress a such the code completion anyway. -- You are receiving this mail because: You are watching all bug changes.
