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

Allinea* Distributed Debugging Tool (DDT) must be configured to run the user application with the necessary Intel libraries preloaded.
Do the following:
  1. Go to the
    dialog box
  2. Select the
  3. In the Session/Options menu, choose
    Intel MPI Library
    and the
    Submit through queue or configure own mpirun command option
  4. In the
    Submit Command
    box enter without line breaks:
    $ mpirun -genv LD_PRELOAD libVTmc.so -genv VT_DEADLOCK_TIMEOUT 20s -genv VT_DEADLOCK_WARNING 25s -n NUM_PROCS_TAG DDTPATH_TAG/bin/ddt-debugger
  5. You can leave other boxes empty. Click
  6. To start the application, press the submit button on DDT's job launch dialog box.
  7. When the application is ready, select the
    Control/Add Breakpoint
    menu and add a breakpoint at the
  8. Continue to run and debug your application as normal, the program will stop automatically at
    when an MPI error is detected.
You can use the parallel stack browser to find the processes that are stopped and select any of these processes. The local variables in this function will identify the error type, the number of errors so far, and the error message.
You can also set a condition on this breakpoint from the Breakpoints tab, or
Add Breakpoint
menu, for example, to stop only after 20 errors are reported use a condition of
reportnumber > 20
See Also

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