• 9.1 Update 2
  • 11/11/2015
  • Public Content

Detecting and Resolving Errors


To demonstrate the process of correctness checking of MPI applications, this tutorial uses two sample applications that have errors in the source code. All the sample applications eligible for correctness checking are available at:
<install-dir>/examples/checking
. You can use these samples to manually experiment with the functionality using the workflow described here.
Read the topics below to learn how to configure the correctness checker and how to detect and resolve application errors using Intel® Trace Analyzer and Collector.
A list of Intel® Trace Collector configuration options for controlling the correctness checking process.
A case where the types of data sent and received do not match, while the number of bytes sent is the same.
Example 2:
Deadlock
A case where two processes simultaneously call blocking receive functions, making them unable to call the succeeding sending functions, which causes the so-called deadlock.
 

Product and Performance Information

1

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