https://bugs.kde.org/show_bug.cgi?id=382771
--- Comment #5 from Daniel Santos <daniel.san...@pobox.com> --- (In reply to Kevin Funk from comment #4) > I can't find a bug report with a similar backtrace from Upstream. > > Could you provide a bit more information? > - Which project are you working on? Can you share? This is just the current HEAD of gcc: https://github.com/gcc-mirror/gcc > - Could you try to figure out which file KDevelop crashes on? The last lines > of the debug output of kdevelop should tell you what it is currently parsing. I didn't see output in stdout or stderr, do you mean in the backtrace? I admit I was surprised by the length of that and never got to the end of it. The file gcc-git.kdev4 has the list of files I excluded from the project so that the parser would only parse libs and archs that I was working on. It's running if I disable the parser, but KDevelop's parsing is something that I've always appreciated, even if it crashes sometimes. Please let me know if you are unable to reproduce and I'll try again. I have since rebuilt llvm and clang with -ggdb. -- You are receiving this mail because: You are watching all bug changes.
