Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Re: Need to know how to debug the indexer

Now this produces output in the console window.

The indexer complains a lot about not being able to apply constants declared in enum declarations. I see it includes a lot of files right up to the point where it includes my problem file. It just stops with no further output to the console window. It looks like I definitely will have to get out the debugger.

Thanks for the info Markus.

Schorn, Markus wrote:
Hi Ray,
If the IDE hangs it is always a good idea to create stack-traces.
* That is easy on a unix system, use:  kill -QUIT process_id.
* Another way (that works on Windwos also) is by using Sun's JDK 1.5:
  Run the IDE with the JVM option, then
  you can use the jconsole (part of JDK 1.5) to connect to the hanging
  IDE and inspect the current stack traces.

The options for tracing the indexing have been refined
(see, you can use
  # Reports sequence of files indexed

  # Reports statistics for indexer

  # Reports problems for indexer


-----Original Message-----
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Ray Hurst
Sent: Donnerstag, 08. Februar 2007 18:55
To: cdt-dev@xxxxxxxxxxx
Subject: [cdt-dev] Need to know how to debug the indexer

It seems that there was a discussion a while back on how to debug the indxer and adding some code to support a logging function. Did anything happen?

I have a project with 400+ files and the indexer always hangs on a particular file. I typed on the command line "gcc - E -P -v -dD include-dirs file.c" and an output is generated with no errors. How do I determine what the indexer is doing?

How do I go about debugging this?
   My System
   Windows XP
   Eclispe SDK 3.3M4
   CDT SDK 4.0.0M4

What I have tried:
   Created a .options file containing the following:

I executed the following command
   eclipse -debug .options

The results:
An extra DOS console window opened up and printed several diagnostic messages up to the point of loading the project. Nothing else printed afterwards. Nothing printed during the Rebuild Index operation.

Do I need to add the entire CDT as a project and run it in debug mode?

cdt-dev mailing list

Back to the top