Set breakpoints for problems in a result to investigate with the debugger.
-create-breakpoints <string> | ALL
A string identifying one or more problems where breakpoints should be inserted. List problems in the form P<n>, where P<n> is a problem identifier in the result problem list. Specify multiple problems as a comma-separated string (no spaces), or use ALL.
Use the create-breakpoints action to specify problems in a result that you want to investigate with the debugger.
This is a three-step process.
Run a collect action using a memory or threading analysis type.
Run a create-breakpoints action to add breakpoints for specified problems to the result of the previous collect action.
Run another collect action, using the same analysis type. Make sure the original result is used as the baseline result, and use the debug-this action-option to enable the debugger.
The debugger is not supported for the mi1 analysis type.
Perform a memory analysis and save the result as r000mi3.
$ inspxe-cl -collect mi3 -result-dir r000mi3 -- ./a.out
This command creates a breakpoint for problem P10 in the result from the previous analysis.
$ inspxe-cl -create-breakpoints P10 -result-dir r000mi3
This command re-runs the analysis in debug mode. The debugger breaks at the P10 breakpoint that was created in the previous step.
$ inspxe-cl -collect mi3 -debug-this -baseline-result r000mi3 -result-dir r001mi3 -- ./a.out