|AW: [cdt-dev] Debugging C/C++ Indexer problems|
it did work for me "out of the box" with the restriction that the source lookup may be working only for one plugin. When you create the "Remote Java Application" launch configuration you must specify the project (=plugin project) you want to debug. I assumed that source lookup and breakpoints will be working for this project only. I did not really try it.
So you may have to decide which plugin you want to debug in at the start of the session.
It's been some time, I only do this if I absolutely have to :-)
Von: cdt-dev-bounces@xxxxxxxxxxx [mailto:cdt-dev-bounces@xxxxxxxxxxx] Im Auftrag von James Blackburn
Gesendet: Donnerstag, 28. September 2006 10:15
An: CDT General developers list.
Betreff: RE: [cdt-dev] Debugging C/C++ Indexer problems
I've tried doing the remote debug on several occasions, and I can attach, view variables etc. However for the life of me I can't get it to find the source. All users are using a shared install (plugins are packaged with the source, etc...).
Have you managed to remote debug the platform and have this work?
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 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