Version: (using KDE KDE 3.1) Installed from: Compiled From Sources Compiler: gcc 3.2 OS: Linux hi guys. I've just tried to load the kopete.kdevelop from our CVS, after another developer has been using it, so the project file is full of his paths. Normally this works for me. Note the file is a clean checkout, not resulting from a CVS merge, so it should be the legal project file that the other developer's gideon wrote. What happened was that instead of parsing the project files as normal, or giving an error that paths in the project file could not be found, gideon started parsing my entire $HOME, and traversed into my 10Gb mp3 partition. Gideon started 'parsing' those and my entire system ground to a halt: OOM. This is unsafe behaviour and should be guarded against. The offending project and session files are at http://www.cs.ncl.ac.uk/old/people/william.stephenson/home.informal/kopete.kdevelop http://www.cs.ncl.ac.uk/old/people/william.stephenson/home.informal/kopete.kdevses
Please not that *.kdevses files should never go into CVS because they store the user's current session only. Can you remember the status message you got while parsing? Was KDevelop trying to build the persistant classstore out of your $HOME or a documentation index?
need more info, but surely this could be more user-proof :)
Harald: Not sure how to tell what was happening. I haven't seen it since. It's whatever class flyout on the left side of the UI is called, as it happened when the project was being opened, and when the files are being parsed you can't expand the class tree there. The status message was "Currently parsing: blah/blah/blah.cpp". The .kdevses was not in cvs, it was the one I had hanging around locally from my last session. Eray: What other info can I provide? You could checkout kdenonbeta/kopete -r'the-time-of-the-first-report'. regards Will
Solved by Roberto Raggi
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