https://bugs.kde.org/show_bug.cgi?id=386720
--- Comment #6 from Angelo Puglisi <angelopuglis...@msn.com> --- (In reply to Milian Wolff from comment #5) > Is the first kind of output repeating, even while you think kdevelop is > frozen? Then it's not frozen and actually does useful work. You simply need > to wait. It should take roughly (hopefully a bit less) as long to parse the > project in KDevelop as it would take to compile it. > > It would only be a bug if you'd see this output stopping at some files and > not going anywhere, while CPU usage is high. > > The last kind of output is OK, it's internal debug output and expected. You > can ignore it. My kdevelop is not frozen, it's still working but the parser is stuck at 0% and I have the parser thread at 100% all the time (I mean my whole working day). Except from the last line I have no other output. I tried to reproduce the issue with a simpler project, including some boost headers I use, but I have only a cpu peak for a couple of seconds and then it stops. I'll try to figure out something to be helpful -- You are receiving this mail because: You are watching all bug changes.
