Investigate Problem Using Interactive Debugging

If you are using the Visual Studio* IDE, you can investigate a problem more deeply with an interactive debugging session during analysis.

Launch an Interactive Debugging Session

In the Problems pane on the Summary window, right-click the data row for the Uninitialized memory access problem set to display a context menu, then choose Debug this problem to:

  • Launch a new analysis, of the same type, optimized to detect only the Uninitialized memory access problem.

  • Halt application execution and open a debugging session when the Intel Inspector detects the first (and only) occurrence the Uninitialized memory access problem.

Note

If the Intel Inspector tells you to rebuild the project, click the OK button to continue using the original build.

Debugger window

1

Intel Inspector launches a new analysis, r001mi2, with the same configuration settings used to create the r000mi2 result, except the analysis is optimized to detect only the Uninitialized memory access problem.

2

Intel Inspector halts execution and opens a debugging session when it detects the Uninitialized memory access problem. In the Visual Studio* IDE, this problem breakpoint is indicated by a yellow arrow at the appropriate source line.

3

The Problem Details pane appears when the problem breakpoint occurs. Use this pane to view the same problem details found in the Intel Inspector result, duplicated within the debugger workspace for convenient referencing while you examine the application state for debugging purposes.

Experiment Using Standard Debugging Commands

During the interactive debugging session, use the normal Visual Studio* debugger actions to examine memory and other state information, set code breakpoints, and continue execution. Only the use of data breakpoints is not supported.

Stop the Analysis and Interactive Debugging Session

When you are finished experimenting in the debugger workspace, stop both the interactive debugging session and the analysis:

  1. Click the Intel Inspector button on the Problem Details pane to display the still-running r001mi2 result.

  2. Click the Stop button on the Intel Inspector Command toolbar.

  3. Click the Collection Log button for the new r001mi2 result to wait for finalization to complete.

When finalization is complete, the Intel Inspector displays a Summary window for the new r001mi2 result that contains only the Uninitialized memory access problem.

Tip

Intel Inspector automatically adjusts the debugging session analysis to return to the Uninitialized memory access problem more quickly; however the analysis adjustments do not correspond to individual problem types. Consequently, the Intel Inspector may detect and report additional problems, but it will break only for the Uninitialized memory access problem.


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

For more complete information about compiler optimizations, see our Optimization Notice.