Investigating Problems Using Interactive
Allow quick investigation of problem(s) of interest.
In a result, choose a problem(s) in the
Summarywindow, right-click to display a context menu, then choose
Debug This Problem.
Typical scenario: After reviewing a problem using result data provided by the
Intel Inspector, you discover you need more application state information at the time the problem occurred, such as the contents of variables. The
Debug This Problemfunction returns you to the point of the problem, halting execution in a debugging session so you can examine memory and other state information at any point in the call stack.
Delay problem detection until a selected point in the application.
In the Visual Studio* debugger, set a code breakpoint to halt application execution prior to where you want analysis to begin. In the
Intel Inspector, select the
Select analysis start location with debuggerradio button when configuring an analysis and start the analysis. Wait for the debugging session to open and execution to halt at the code breakpoint. Choose to turn on analysis and resume execution.
Outcome: Execution halts for each problem detected after you turn on analysis and resume execution. You cannot turn off analysis again.
Typical scenario: You configured the project to limit the application modules for inspection, but you need to narrow analysis focus even further. This option lets you choose an arbitrary location to turn on error detection, allowing faster execution until that point.
Because debugging in conjunction with a threading analysis significantly slows execution:
Allow investigation of every detected problem.
Intel Inspector, select the
Enable debugger when problem detectedradio button when configuring an analysis.
Outcome: When you run the analysis, the
Intel Inspectorhalts application execution when it detects the first problem and launches a debugging session. Execution halts for each detected problem when you resume execution using normal debugger commands.
Typical scenario: You want to investigate the state of the application for every problem detected.
Because of analysis speed issues, this option is not recommended when detecting data races. It is faster to use the
Debug This Problemfunction to selectively investigate threading problems identified during a non-debug run.
- Intel Inspectorsupports interactive debugging only for pure native applications.
- Intel Inspectordoes not offer interactive debugging for theDetect Leaks(mi1) analysis type because memory and resource leaks are determined after an application terminates and therefore cannot be used to halt execution during analysis. However, you can perform a standard debugger attach to a process launched under this analysis type.
- Do not recompile your application after generating a result if you plan to use the resultDebug This Problemfunction.Intel Inspectorcannot guarantee finding the same problem(s) when the binary changes; consequently, it checks for a binary change and reports a warning to prevent rerunning an analysis that may not stop at the selected problem(s).
- When you use theDebug This Problemfunction, the problem list in the new result may differ from the problem list in the source result.Intel Inspectorautomatically adjusts the debugging session analysis to return to the selected problem(s) more quickly; however the analysis adjustments do not correspond to individual problem types. Consequently, theIntel Inspectormay detect and report additional problems, but it will break only for a selected problem(s).