Investigate Problem Using Interactive Debugging

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, 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.

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

Debugger window

The debugger displays problem breakpoint information in a prob-brk-id: prob_brk_desc format, where:

  • prob-brk-id is a debugger-assigned integer value that identifies the problem breakpoint.

  • prob-brk-desc is a short problem description.


Do not confuse the prob-brk-id values assigned by the debugger with problem IDs prefaced with the letter P in the Intel Inspector result data.

Display Extended Debugging Commands

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

Intel Inspector also offers a set of command extensions to use within an interactive debugging session during analysis. Type monitor help to view a list applicable to memory error analyses:
Debugger window

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. Return to the Intel Inspector window. Notice the new, still-running, r001mi2 result.

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

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


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.