Skip to main content

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

As I mentioned, I use the source out of CVS. Theoretically you can use the
CDT SDK feature to do it, but I haven't tried that. In that case you would
import the cdt plugins as binary plugins (and not the source plugins since
the source lookup is handled automagically).

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


> -----Original Message-----
> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Ray Hurst
> Sent: Thursday, February 08, 2007 1:58 PM
> To: cdt-dev@xxxxxxxxxxx
> Subject: [cdt-dev] Re: Need to know how to debug the indexer
> 
> Doug,
> I have the SDK installed.
> 
> I seem to remember that I need to use the Import->Plugins and Fragments
> option.
> 
> Do I need to import all of the CDT modules or can I just import the
> source modules.
> Ray
> 
> Doug Schaefer wrote:
> > No problem. There are the hardest things for us to debug because we
> usually
> > need to replicate your environment. Please raise a bug if you find out
> > anything.
> >
> > Cheers,
> > Doug Schaefer, QNX Software Systems
> > Eclipse CDT Project Lead, Tools PMC Member
> >
> >
> >> -----Original Message-----
> >> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
> On
> >> Behalf Of Ray Hurst
> >> Sent: Thursday, February 08, 2007 1:09 PM
> >> To: cdt-dev@xxxxxxxxxxx
> >> Subject: [cdt-dev] Re: Need to know how to debug the indexer
> >>
> >> Thanks Doug. I was hoping you would answer.
> >> Ray
> >>
> >> Doug Schaefer wrote:
> >>> Well, what I would do is download the Eclipse SDK. Check out of CVS
> the
> >>> source to the particular version of the CDT that experiences the hang
> >> (BTW,
> >>> the Eclipse SDK version needs be correct as well).
> >>>
> >>> Launch an Eclipse Application under the debugger. When the indexer
> >> hangs,
> >>> hit the suspend button for the whole session. Then take a look at each
> >>> thread to see if they were stopped somewhere interesting.
> >>>
> >>> You'd have to play around with it a bit to see if it's really hung, or
> >> just
> >>> taking a long time, and whether it is hung because of a deadlock (i.e.
> >> all
> >>> of the threads were in a wait), or an infinite loop somewhere in the
> >> parser
> >>> or indexer.
> >>>
> >>> Doug Schaefer, QNX Software Systems
> >>> Eclipse CDT Project Lead, Tools PMC Member
> >>>
> >>>
> >>>> -----Original Message-----
> >>>> From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-
> bounces@xxxxxxxxxxx]
> >> On
> >>>> Behalf Of Ray Hurst
> >>>> Sent: Thursday, February 08, 2007 12:55 PM
> >>>> 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?
> >>>> Ray
> >>>>
> >>>> 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:
> >>>>      org.eclipse.cdt.core/debug/pdomtimings=true
> >>>>      org.eclipse.cdt.core/debug/indexer=true
> >>>>      org.eclipse.cdt.core/debug/parser=true
> >>>>      org.eclipse.cdt.core/debug/deltaprocessor=true
> >>>>      org.eclipse.cdt.core/debug/scanner=true
> >>>>      org.eclipse.cdt.core/debug/model=true
> >>>>
> >>>> 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?
> >>>> Ray
> >>>>
> >>>> _______________________________________________
> >>>> cdt-dev mailing list
> >>>> cdt-dev@xxxxxxxxxxx
> >>>> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> >> _______________________________________________
> >> cdt-dev mailing list
> >> cdt-dev@xxxxxxxxxxx
> >> https://dev.eclipse.org/mailman/listinfo/cdt-dev
> 
> _______________________________________________
> cdt-dev mailing list
> cdt-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/cdt-dev


Back to the top