Since HPC applications target high performance, users are interested in analyzing the runtime performance of such applications. In order to get a representative picture of that performance / behavior, it can be important to gather analysis data at the same scale as regular production runs. Doing so however, would imply that shared memory- focused analysis types would be done on each individual node of the run in parallel. This might not be in the user’s best interest, especially since the behavior of a well-balanced MPI application should be very similar across all nodes.
Intel® Inspector is a dynamic memory and threading error checking tool for users developing serial and multithreaded applications on Windows* and Linux* operating systems. This topic is part of a tutorial that shows how to find and fix threading errors using the Intel Inspector and a C++ sample application.
analysis: A process during which the Intel Inspector performs collection and finalization.
code location: A fact the Intel Inspector observes at a source code location, such as a write code location. Previously called an observation.
collection: A process during which the Intel Inspector executes an application, identifies issues that may need handling, and collects those issues in a result.
Prerequisite: Configure debug mode with the optimal compiler and linker settings to produce the most accurate and complete Intel Inspector analysis results:
Intel Inspector offers a range of preset threading analysis types to help you control analysis scope and cost:
Analysis types with the narrowest scope minimize the load on the system and the time and resources required to perform the analysis; however, they detect the narrowest set of errors and provide minimal details.
Do one of the following in the Intel InspectorProblems pane:
To Do This
Use the Create Problem Report option on Intel InspectorSummary window context menus to export result data in plain text format so you can distribute it to teammates in other media, such as email.
This functionality provides more data and versatility than the Copy to Clipboard option available on various context menus.
There are two typical usage models for handling handwritten suppression files in the Intel Inspector. They differ depending on how you want to confirm the effectiveness of the files:
Apply the handwritten file to an existing result, check the resulting strikethrough marks, then continue editing the file in the text editor as necessary.