Bug 3583 - investigate cdt parser update
Summary: investigate cdt parser update
Alias: None
Product: frysk
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
: P2 normal
Target Milestone: ---
Assignee: Rick Moseley
Depends on:
Blocks: 3392
  Show dependency treegraph
Reported: 2006-11-24 15:43 UTC by Andrew Cagney
Modified: 2008-04-03 20:59 UTC (History)
1 user (show)

See Also:
Last reconfirmed:


Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Cagney 2006-11-24 15:43:21 UTC
Apparently frysk's snapshot is a full release behind.  Andrew-O might be worth
pinging since he co-ordinates eclipse builds and the like.


This bug is to record the exact status and resolution, if the decision is to
import I'd create a tracker for that (hung off of Bug #3392)
Comment 1 Mike Cvet 2006-12-04 22:59:55 UTC
Re: #3643, it ends up that the CDTParser was not mindlessly spinning - it was 
actually parsing the code, just slowly. 

According to Rick's initial timing with a testing standalone parser, parsing 
the approximately 780k of johntheripper source code took about 4.5 minutes. I 
attempted running the SourceWindow on that code a similar length of time and 
can verify those results. 

Setting parsing mode to "full parse" in eclipse appears to be nearly snappy.
Comment 2 Rick Moseley 2006-12-05 19:38:24 UTC
This was a bug in the way include paths were being added to the DOM.  Some
include paths were being added multiple times forcing the parser to create
readers and parser those paths multiple times, thereby causing the slowdown.

Changes have been made to DOMFactory.java to keep this from happening.  Tests
now show the time to parse johntheripper dropped from 4.5 minutes to about .5
Comment 3 Rick Moseley 2006-12-06 21:37:25 UTC
Sorry.  The previous comment was meant for a different bug.

Currently we are using a version of the CDT Parser cut from version 2.0 of the
Eclipse CDT.  This version allowed iteself to be used as a stand-alone parser
that could be instantiated and used by other programs.

Since then, the CDT Parser has been totally redesigned and split into 2 pieces,
an indexer and a parser.  I'm not sure what exactly each piece does.  During the
rewrite the new parser has been made more dependent on elements in the eclipse
core making it virtually impossible to use in a stand-alone mode.

There is a move afoot to resolve this and a bugzilla has been filed for this
action here:


This effort is ongoing.  I will try to find out what is happening with this and
if this has occurred yet.  The last comment in this bugzilla was in Oct. 2006,
so maybe they have made some progress.
Comment 4 Rick Moseley 2007-07-17 14:00:04 UTC
After sending an e-mail to Mike Kucera of IBM who posted links to some of the
latest CDT Parser documentation, he verified there is a new stand-alone version
of the CDTParser being used inside of IBM.  He requested I send an e-mail to the
cdt-dev list and ask for some help in this.
Comment 5 Rick Moseley 2008-04-03 20:59:15 UTC
The decision has been made to remove the cdt parser.  A new bug has been opened
for this.  See bug 5826.