|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 http://wiki.eclipse.org/index.php/FAQ_How_do_I_use_the_platform_debug_tracing_facility%3F 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.
See http://java.sun.com/j2se/1.5.0/docs/tooldocs/windows/java.html#options and http://java.sun.com/j2se/1.5.0/docs/guide/jpda/conninv.html, section "Sun VM Invocation Options" for more info.
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von Delicia
Gesendet: Mittwoch, 27. September 2006 16:16
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.
Back to the top