This tutorial demonstrated an end-to-end workflow you can ultimately apply to your own applications.


Tutorial Recap

Key Tutorial Take-aways

1. Set up

If you used the Visual Studio* IDE: You chose a project; verified the project is set to produce the most accurate and complete analysis results; built and ensured the application runs on your system outside the Intel Inspector.

If you used the standalone GUI: You built and ensured the application runs on your system outside the Intel Inspector, and created a project to hold analysis results.

Applications compiled and linked in debug mode using the following options produce the most accurate and complete analysis results: /Zi or /ZI, /Od, /MD or /MDd, and no /RTC.

2. Collect result

You chose an analysis type and ran an analysis. During analysis, the Intel Inspector:

  • Ran the application, identified errors that may need handling, collected a result, and displayed the result in a result tab.

  • Added a pointer to the result in the Solution Explorer (Visual Studio* IDE) or Project Navigator (standalone GUI).

  • Intel Inspector offers preset analysis types to help you control analysis scope and cost. Widening analysis scope maximizes the load on the system, and the time and resources required to perform the analysis.

  • Run error analyses from the Tools menu (Visual Studio* IDE), File menu (Standalone Intel Inspector GUI), toolbar, or command line using the inspxe-cl command.

3. Investigate result

You explored detected problems, interpreted the result data, accessed an editor directly from the Intel Inspector, and changed source code. You also investigated a problem using interactive debugging if you used the Visual Studio* IDE.

  • Key terms: A code location is a fact the Intel Inspector observes at a source code location. A problem is one or more occurrences of a detected issue. A problem set is a group of problems with a common problem type and a shared code location that might share a common solution.

  • Think of the Problems pane on the Summary window as a to-do list: Start at the top and work your way down.

  • Double-click a code location or problem on the Summary window to navigate to the Sources window. Click the Summary button on the Sources window to return to the Summary window.

  • Right-click various places on the Summary or Sources window to display a context menu, then choose Explain Problem to access more information on interpreting and resolving the problem.

  • Double-click a code location on the Sources window to open an editor.

  • Right-click a problem, then choose Debug This Problem to launch an interactive debugging session (Visual Studio* IDE).

4. Check your work

You recompiled, relinked, and reinspected the application.

Next step: Prepare your own application(s) for analysis. Then use the Intel Inspector to find and fix errors.

Studio-specific supplemental documentation may be available at <install-dir>\<studio>\documentation\ .

Einzelheiten zur Compiler-Optimierung finden Sie in unserem Optimierungshinweis.