Summary: | OUT OF MEMORY: loading project causes attempt to parse $HOME as project | ||
---|---|---|---|
Product: | [Applications] kdevelop | Reporter: | Will Stephenson <wstephenson> |
Component: | Language Support: CPP (old) | Assignee: | KDevelop Developers <kdevelop-devel> |
Status: | RESOLVED FIXED | ||
Severity: | crash | ||
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
Will Stephenson
2003-02-06 13:16:13 UTC
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 |