• 2019 Update 3
  • 03/07/2019
  • Public Content
  • Download as PDF

To automate the procedure of setting breakpoints, GNU* Symbolic Debugger (GDB) supports executing commands automatically. To apply setting this breakpoint for all programs in the current working directory, you can create a file
with the following lines (or add them if it already exists):
set breakpoint pending on break MessageCheckingBreakpoint
Due to the order in which files are processed, placing the same commands in a
file in the home directory does not work because the main binary is not loaded yet. As a workaround, you can put the following commands into
define hook-run # important, output is expected by MPI startup helper echo Starting program... # allow pending breakpoint set breakpoint pending on # set breakpoint now or as soon as function becomes available break MessageCheckingBreakpoint # restore default behavior set breakpoint pending auto end
Then start your MPI application as follows:
$ mpirun -check_mpi -gdb -n <numprocs> <app>

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804