Tutorial: Analyzing Threading Errors with Intel® Inspector and a C++ Sample
Investigate a problem more deeply with an interactive debugging session during analysis.
In the Problems pane on the Summary window, right-click the data row for the Data race problem set in the xvideo.cpp source file to display a context menu, then choose Debug this problem to:
Launch a new analysis, r001ti2, with the same configuration settings used to create the r000ti2 result, except the analysis is optimized to detect only the Data race problems in the xvideo.h source file.
Halt application execution and open a debugging session when the Intel Inspector detects the first occurrence of the Data race problems.
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.
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 threading error analyses:
When you are finished experimenting in the debugger workspace, stop both the interactive debugging session and the analysis:
Return to the Intel Inspector window. Notice the new, still-running, r001ti2 result.
Click the Stop button on the Intel Inspector Command toolbar.
When finalization is complete, the Intel Inspector displays a Summary window for the new r001ti2 result that contains only the Data race problems in the xvideo.cpp source file.
Intel Inspector automatically adjusts the debugging session analysis to return to the Data race problems 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 Data race problems in the xvideo.cpp source file.