Contents
IA-32/Intel® 64 Architecture debugging
The GNU* Project Debugger (GDB) provided with the Intel® Parallel Studio XE Composer Edition is based on GDB with enhancements provided by Intel.
It can debug applications:
Debug applications natively on IA-32 or Intel® 64 Architecture systems.
Always source the following script in the same environment where you use the debugger:
source <install-dir>/bin/compilervars.sh
<install-dir> is the installation directory, by default, it is:
For other prerequisites, new debugger features, hardware and software requirements, and known issues refer to the release notes.
To debug applications natively on IA-32 or Intel® 64 Architecture systems, start GDB with the following command:
gdb-ia
The actual debugger usage is the same as for the GNU* Project Debugger. Extensions for IA-32/Intel® 64Architecture are described in the debugger documentation.
Debug applications remotely on Intel® Xeon Phi™ coprocessor systems.
The debugger runs on a host system and a debug agent (gdbserver) runs on the coprocessor. There are two options:
Always source the following script in the same environment where you use the debugger:
source <install-dir>/bin/compilervars.sh
<install_dir> is the installation directory, by default, it is:
For other prerequisites, new debugger features, hardware and software requirements, and known issues refer to the release notes.
Debugging applications for the Intel® Xeon Phi™ coprocessor is like debugging a remote Intel® 64 application:
The host is running the debugger GNU* GDB. This system can be the host containing the coprocessor cards or any other development host.
The target, here the coprocessor itself, executes a debug agent (gdbserver) to which the host connects to.
For more information on debugging on the Intel® Xeon Phi™ coprocessor, see also http://software.intel.com/en-us/articles/debugging-intel-xeon-phi-applications-on-linux-host.
You can either start the debugger from the command line or from Eclipse* IDE.
Starting the debugger from the command line:
$ scp <install_dir>/debugger_<product_version>/gdb/targets/intel64/x200/bin/gdbserver "mic0:/tmp"
<install_dir> is the installation directory, by default, it is:
$ gdb-ia (gdb) target extended-remote | ssh mic0 /tmp/gdbserver --multi –
(gdb) file <path_on_host>/<application> (gdb) set remote exec-file <path_on_target>/<application>
(gdb) <file> <path_on_host>/<application> (gdb) attach <pid>
Starting the debugger from Eclipse* IDE:
AMPLXE_COI_DEBUG_SUPPORT=TRUE MYO_WATCHDOG_MONITOR=-1
Configuring Eclipse* for Debugging Fortran Applications with GDB:
Document | Description |
---|---|
GDB Manual | Contains descriptions of the GNU* Debugger (GDB) functions and interfaces including Intel-extended features for debugging applications natively on IA-32 or Intel® 64 Architecture systems. |
GDB Manual in Info format | To read the GDB Manual in the Info format, use the following command: info gdb-ia |
GDB man pages | To access the GDB man pages, set the environment variables by sourcing the compiler environment script, compilervars.sh, and use the following command: man gdb-ia |
Intel® Parallel Studio XE 2018 Composer Edition Fortran - Debug Solutions Release Notes Intel® Parallel Studio XE 2018 Composer Edition C++ - Debug Solutions Release Notes |
Release Notes for debugging with Intel® Parallel Studio XE. |
Intel® Parallel Studio XE | Intel® Parallel Studio XE product page. See this page for support and online documentation. |
No license (express or implied, by estoppel or otherwise) to any intellectual property rights is granted by this document. Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade. This document contains information on products, services and/or processes in development. All information provided here is subject to change without notice. Contact your Intel representative to obtain the latest forecast, schedule, specifications and roadmaps. The products and services described may contain defects or errors known as errata which may cause deviations from published specifications. Current characterized errata are available on request.
Intel, the Intel logo, Xeon, and Intel Xeon Phi are trademarks of Intel Corporation in the U.S. and/or other countries.
*Other names and brands may be claimed as the property of others.
© 2017, Intel Corporation