Community
Participate
Working Groups
There are some problems with working with CDT in Eclipse: 1) C code parser working with unacceptable priority and increasing latency of interaction with editor when opening new file and trying to scroll or edit it 2) Disabled caching of already parsed files then parsing takes some time in every opening of file 3) Some erorrs in parsing of syntaxically correct files (File with parser log is attached) 4) Growing memory consumage and consequent fatal errors I have Eclipse CDT 2.0M8 P.S. If necessary I can contribute to your project. I have high skills in Java, Eclipse and highly motivated to have uniplatform C/C++ IDE.
Created attachment 10478 [details] ~/workspace/.metadata/.plugins/org.eclipse.cdt.core/.log
1. What are your preferences for the C++ editor? Are you asking the CModel builder to follow includes? The default is off for a reason (performance). If you are not following includes and you find that latency increases as you scroll, please attach a sample that does so. 2. We do wish to cache the inclusions : it requires our entire framework to be persistable, in order to scale for large workspaces. This is a challenge that is not in the 2.0 timeframe unfortunately. 3. The parser log attached indicates only preprocessor errors. Do you have your include paths set up properly? What compiler are you using? Are you using Standard or Managed Make? 4. Memory consumption is a concern and I am attempting to address it in order to address scalability in the 2.0 timeframe. Off the record, M8 is a pretty bad build for memory usage (both the Eclipse Platform and the CDT). If you are interested in contributing to the discussion of how we can make our parser framework scale and perform, subscribe to the CC of defect 57816 and give your 2 cents. If you are interested in contributing code, even better.
>1. What are your preferences for the C++ editor? Are you asking the CModel >builder to follow includes? The default is off for a reason (performance). >If you are not following includes and you find that latency increases as you >scroll, please attach a sample that does so. There are only two options in Preferences for this: a) Search current file and included files, and b) Search current project I choosed second one, but nothing changed >3. The parser log attached indicates only preprocessor errors. Do you have >your include paths set up properly? What compiler are you using? Are you >using Standard or Managed Make? I trying to resolve source of this problem. gcc. Standard Make
Dmitry, when our M9 becomes available please give it a try and let us know if things work better for you. The type-cache that was continually parsing the working copy has been tamed to not do so. I also would recommend using the scanner discovery feature that allows for Standard Make projects to have their include paths imported into the project properties so to better aid the parser.
Dmitry, CDT M9 is now available. Give it a whirl and let us know the status of this problem. Thanks.
Moving this to 2.0.1. We are defering parser related performance issues to 2.0.1. Some of this defect is likely associated with 59468, which is the "magic Parser performance" defect.
I believe this should be fixed. Dmitry, please re-open the defect if you can reproduce the problem using a CDT 2.0.1 loadbuild.
