Installation guide
Intel® Parallel Studio XE 2015 Composer Edition for C++ Linux*
Installation Guide and Release Notes 26
4.2 Using GNU* GDB
GNU* GDB provided with Intel® Parallel Studio XE 2015 comes in different versions:
IA-32/Intel® 64 debugger:
Debug applications natively on IA-32 or Intel® 64 systems with gdb-ia on the
command line.
A standard Eclipse* IDE can be used for this as well if a graphical user interface is
desired.
Intel® Xeon Phi™ coprocessor debugger:
Debug applications remotely on Intel® Xeon Phi™ coprocessor systems. The debugger
will run on a host system and a debug agent (gdbserver) on the coprocessor.
There are two options:
o Use the command line version of the debugger with gdb-mic. This only works
for native Intel® Xeon Phi coprocessor applications.
A standard Eclipse* IDE can be used for this as well if a graphical user interface
is desired.
o Use an Eclipse* IDE plugin shipped with Intel® Parallel Studio XE 2015. This
works only for offload enabled Intel® Xeon Phi coprocessor applications.
Instructions on how to use GNU* GDB can be found in the Documentation section.
4.3 Documentation
The documentation for the provided GNU* GDB can be found here:
<install-dir>/Documentation/[en_US|ja_JP]/debugger/gdb/gdb.pdf
<install-dir>/Documentation/[en_US|ja_JP]/debugger/
gdb/gdb_quickstart_lin.pdf
4.4 Known Issues and Changes
4.4.1 Problem using Eclipse* IDE with GDB*
If the GNU* GDB version that is provided by Intel is used within an Eclipse* IDE, you need to
setup the environment before starting Eclipse* as described in the section on Establishing the
Compiler Environment.
4.4.2 Safely ending offload debug sessions
To avoid issues like orphan processes or stale debugger windows when ending offload
applications, manually end the debugging session before the application is reaching its exit
code. The following procedure is recommended for terminating a debug session.
Manually stop a debug session before the application reaches the exit-code.
When stopped, press the red stop button in the toolbar in the Intel® MIC Architecture-
side debugger first. This will end the offloaded part of the application.
Next, do the same in the CPU-side debugger.