Debugging via Console

If your binary runs on the asl-cluster, you have direct acces to gdb:

• Debugging via Console

If our binary runs on a FEC, you are forced to use remote-debugging:

• Remote-Debugging via Console

GDB Cheat Sheet

Instruction on how to use GDB are found here: GDBCheatSheet.

Debugging via Eclipse

Required Eclipse Plugins

Terminal - http://elt.googlecode.com/git/update-site Eclipse Indigo - http://download.eclipse.org/releases/indigo

• General Purpose Tools > Remote Systems Explorer End-User Runtime
• Mobile and Device Development > C/C++ GDB Hardware Debugging / C/C++ Remote Launch

General Setup

• Install the Remote Systems Explorer: Remote Systems Explorer End-User Runtime / User Actions from http://download.eclipse.org/releases/indigo, section Mobile and Device Development
• Get the python pretty printers in your home directory: svn co svn://gcc.gnu.org/svn/gcc/trunk/libstdc++-v3/python
• Setup your .gdbinit file (example file attached, adapt the path to your pretty printer installation: e.g. $(HOME)/python)
• Enable pretty printing by adapting Window > Preferences > C/C++ > Debug > GDB, select your .gdbinit file and enable the pretty printing option.

The debug-session

If the computer on which the binary is running is the same computer on which eclipse is running, please continue here:

• Debugging via Eclipse

If this is not the case, continue here:

• Remote-Debugging via Eclipse