Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cdt-dev] As promised, an FAQ start


  Here is some starter text for the expanded FAQ which we were discussing
last week.
I've deliberately kept some of the replies brief since I would like to
solicit input
rather than putting down things that don't make sense to someone new to the

  There is also no sensible order to it as it stands.



Q: I'm missing some basic C/C++ debugging functionality, where is it hidden?

A: You have to customize your debug perspective to see all C/C++ actions. In

the Debug perspective open "Window"-->"Customize perspective"-->"Other" and 
check the "C/C++ Debug" box. In the latest version it is checked by default.

To customize your views open "Window"-->"Preferences"-->"Debug"-->"Debug 
Action Groups" and check/uncheck the "C/C++ Debug" and "Java Debug" boxes.

Q: I just installed Eclipse and the CDT.  However, CDT does not recognize
existing toolchain [ie Visual Studio, Borland, Watcom, Cygwin, MinGW, GCC, 
etc]. How do I make the CDT recognize these tools?

A: The current CDT doesn't integrate with a specific toolchain, but rather 
integrates with a build command, such as make, nmake, jam ant etc and this 
build command drives the toolchain.  The default build command is make, but 
can be configured as part of the project properties.

Q: I don't understand make and I just have some source I want to compile.  
What do I have to do to get there.

A: ...

Q: What is the default configuration supported by the CDT components?

A: This is a bit of a moving target, but the compiler supported (from an
parsing point of view) is gcc, the debugger interface will work with gdb
and the default build command is make

Q: Can I debug remote targets 

A:  There is no specific support for downloading and contacting a remote 
target, but these things can be configured in the .gdbinit if the debugger 
is gdb.  The other option is that it is possible to write your own extended 
launch component which will contain the information needed to talk
with your target configuration.

Q: Since the debugger is gdb, can I simply access the gdb console?

A: Yes, partially.  The console can be flipped into gdb mode (see the "Show 
Debugger Console" button in the debugger view which does this) and you can 
type in commands at that point.  Doing this can possibly de-synchronize the 
IDE with gdb, so you should be careful to what extent you drive the debugger

using this interface.  

Q: Can I see/log all of the commands which are being driven to gdb?

A: Yes, you can turn on tracing for the debug plugin and it will show you
of the information about what commands are being sent to gdb.  To run with 
1. Create a file (for example, .options)
2. Add the following line to it:
3. Start Eclipse with
 	-debug "file:<full path>/.options"

Q: I'd like to use this "code assist" functionality, but it doesn't seem to
for me.  I don't get anything showing up when I select CTRL+SPACE in a C/C++

source file

A: Code assist is a work in progress.  Currently for this capability to
you must enable indexing of the project (which may or may not require the
utility).  Once indexing is enabled, the only code completion which is
(other than code templates) is function completion.  As we improve and
develop this function will get better and better.

Q: Is it possible to see global variables?  The variables view shows only
local variables.

A: The "Variables" view displays only local variables and arguments for the 
selected stack frame. You can use the "Add Expression (C/C++)" option to add

a global variable to the "Expressions" view.

Q: Can I see the raw compiler output?  Where is this information placed?

A: The C-Build view is a console which shows all of the activity which
once a project's build command is executed.

Back to the top