• View
• Edit
• History
• Print

IntelDebugger

Three steps to make the Intel Debugger (idb,idbc) work with the Codelite IDE:

1. Create a script with the following content:

 #
 #!/bin/bash
 #
 #
 #
 # add the path where to find libraries (eg. in the home directory)
 #
 export LD_LIBRARY_PATH=/home/username/project/libs
 #
 # add a library which should be loaded before the app starts
 #
 # (necessary to set pending breakpoints with IDB if shared libraries will be used!)
 #
 # LD_PRELOAD use spaces as delimiter! if you have a space in your path use symbolic links.
 #
 export LD_PRELOAD=/home/username/project/libs/libToPreload.so
 #
 # find intel debugger (idb in version 9.1,idbc since version 11) and set path
 #
 echo "Run the idbc in gdb mode with mi as interpreter."
 #
 export INTEL_DGB=`locate idbc | grep idbc | tail -1`
 #
 # run the IDB in gdb mode and active the Machine Interface Interpreter(-i) to work with Codelite.
 #
 exec $INTEL_DGB -gdb -i=mi "$@"

1. Set the script as a debugger path in Codelite/workspaceView/YourStartProjectSettings/Debugger.
2. Enable "pending breakpoints" and "Use file name only for breakpoints(NO full paths)" in MainMenu/Settings/"Debugger Settings..."

Q: Why you're not using GDB? It is able to debug mixed fortran/c++ code well.

Yes it is as long as the fortran code is linked statically. When you create mixed shared libraries and try to jump into a fortran subroutine GDB fails. The IDB is the only debugger atm. to debug mixed code in shared libraries