Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] Re: Debugging C/C++ Indexer problems

Hi Norbert & James,
Thanks for the suggestions.
I'll need to change quite a bit to make the plugin debuggable.
For that matter, I haven't written my own class for the Scanner Info Provider, I'm using the one available in CDT.
My plugin contains:
         name="My ScannerConfigurationDiscoveryProfile"
      <scannerInfoProvider providerId="specsFile">
               arguments="-E -P -v -dD ${plugin_state_location}/${specs_file}"
James, I don't see the *.sc files in the mentioned directory. It just contains blank files (specs.c & specs.cpp).
Have I missed out on defining some variable?
Thanks again!
P.S. I must mention that the plugin(s) is packaged as a product.
From: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx]
On Behalf Of Ploett, Norbert
Sent: 28 September 2006 07:35
To: CDT General developers list.
Subject: AW: [cdt-dev] Debugging C/C++ Indexer problems

you could ask your colleagues to enable tracing for the relevant plugins
and compare the trace output with yours.
Provided that the authors of the plugins have put in enough tracing calls.
See for more info.
Your colleagues could start their eclipse as a remote debugable java
application and then you coud attach your eclipse as debugger and do all
the fun stuff like setting breakpoints and looking at variable values :-)
This requires a reasonably fast internet connection and no (fire-)walls
and gates to block the java debugger's communication. You must be able
to freely access one port (you choose the number) on the target machine.
and, section
"Sun VM Invocation Options" for more info.
Norbert Ploett

Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im
Auftrag von Delicia
Gesendet: Mittwoch, 27. September 2006 16:16
An: cdt-dev@xxxxxxxxxxx
Betreff: [cdt-dev] Debugging C/C++ Indexer problems

    I've implemented the 'ScannerConfigurationDiscoveryProfile'
extension (mainly by changing gcc TO Mygcc).
The Indexer works nicely on my system & a couple of other PCs I used for testing.
However, my colleagues sitting across the oceans are having problems
with the Indexer. The PATH var setting, looks correct.
Is there any way I can debug what the problem is, and why the Indexer
works here, but not there?
P.S. This applies to managed make projects.
Message: 2
Date: Thu, 28 Sep 2006 01:28:50 -0700
From: "James Blackburn" <jamesb@xxxxxxxxxxxx>
Subject: RE: [cdt-dev] Debugging C/C++ Indexer problems
To: "CDT General developers list." <cdt-dev@xxxxxxxxxxx>

Content-Type: text/plain; charset="us-ascii"

Hi Delicia,
Try and have a look at whether the Includes and Symbols are being
discovered from your colleagues' make output.  They're stored in
.metadata/.plugins/org.eclipse.cdt.make.core/<project>.sc & the
associated <project> scanner generated make file.
Entries picked up by the scanner look like:
<option key="-D" value="MY_VAR=FOO"/>
If they have then made it through the scanner discovery make system,
you'll get an equivalent line:
<siItem kind="SYMBOL_DEFINITION" value="MY_VAR=FOO"/>

Back to the top