Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] FW: [Bug 139583] Internal error in Fast C++ indexer

Here's a great question that will be important to answer for the upcoming
test activity.

In order to debug the CDT to find out where certain exceptions are
occurring, make sure you install the SDK version of the CDT. Start up a new
workspace and import the CDT plugins you need using the Import -> Plugins
and Fragments wizard. For the indexer, import org.eclipse.cdt.core. The
default settings for the import are fine. In the Debug perspective, set a
Java Exception breakpoint on the exception you want to trap. You can also
set a breakpoint anywhere in the plugins you've imported.

Now start up an Eclipse Application Debug session, pointing the workspace
data location to the workspace where you saw the exception. Everything else
is fine. You may want to set the Arguments to match how you normally launch
eclipse (e.g. -clean or the VM arg -Xmx256M).

Now, for the Fast indexer in particular, somewhere up the stack trace you're
going to see a bunch of accepts concluded with a visit which calls the
CASTName or CPPASTName resolveBinding function. Selecting the resolveBinding
call in the stack and clicking on 'this' in the variables view gives you the
name of the symbol. Adding a watch expression that calls getFileLocation()
on the Name will gives you the file name and line number of where the name
resides. This is all valuable information that I can use to help see what
the problem is.

Hope this helps, correct me where I'm incorrect, and I'll make sure I get
this into the wiki somewhere.

Doug Schaefer, QNX Software Systems
Eclipse CDT Project Lead, Tools PMC member

-----Original Message-----
From: bugzilla-daemon@xxxxxxxxxxx [mailto:bugzilla-daemon@xxxxxxxxxxx] 
Sent: Monday, May 01, 2006 3:49 PM
To: dschaefer@xxxxxxx
Subject: [Bug 139583] Internal error in Fast C++ indexer 
Product/Component: CDT / CDT-parser

------- Comment #3 from eclipse.sprigogin@xxxxxxxxx  2006-05-01 15:49
Unfortunately I don't know which file was being processed when the error
happened. I may be able to do some debugging for you if you tell me how.

Configure bugzilla e-mail:
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Back to the top