Version: 3.0.92 and 2.0.4 (using KDE KDE 3.2.3) Installed from: SuSE RPMs Compiler: gcc 3.3.3 OS: Linux www.eisscholle.de/glew.h (400kb) ist part of a larger project( >> 70.000 lines in .cpp files) when loading that project into kdevelop the cpp parser stalls at this file (glew.h) and CPU usage goes up to 98% or completely stalls the system. Loading other files of that project works fine the parsers gets till 51%. GLEW is part of an opengl extension loading library, and the version i used before was loaded successfully in kdevelop. this version doesnt, though. (I spoke to "teatime" on #kdevelop at irc.freenode.org about that). The project is qmake based, kernel is 2.4. GLEW can also be found at (http://glew.sf.net).
Version is 3.0.4 (latest stable) and latest beta2 not 2.0.4. sorry.
Probably glew.h has some strange binary characters on it. Or you have a bad BDB version. What is your BerkeleyDB version
Berkley db is 4.1.25 (db40 is also installed, version 4.0.14) (SuSE9.0 packages)
BDB version is irrelevant in this scenario, it is only used for CodeCompletion databases, not to cache the data for the current project.
On the strange binary characters issue. GCC doesnt complain and compiles the file without any problems, so i think the parser should read it as well. Are there any tools to check for a valid character range?
Any news on this issue? I moved my dev. desktop to windows since its resolved. Or is that just related to that file and not of any value to others?
Oldest I found so far, but let's dupe it against the one with the best discussion and a potential workaround. *** This bug has been marked as a duplicate of 96909 ***
Moving all the bugs from the CPP Parser. It was not well defined the difference between it and C++ Language Support and people kept reporting in both places indistinctively