Visible to Intel only — GUID: GUID-ED282ACB-513A-4096-878B-BBD191F42498
Visible to Intel only — GUID: GUID-ED282ACB-513A-4096-878B-BBD191F42498
appdebug
Set when to enable the debugger.
-appdebug <value> |
off |
Do not connect to debugger. |
on-start |
Connect to debugger when the application starts. |
on-error |
Connect to debugger when an application error is detected. |
delay-analysis |
(off) |
Off
Use the appdebug action-option to set when to stop application execution and connect the application to the debugger. Useful for examining application state when Intel Inspector detects recognized problem types (break events).
The GNU gdb* debugger is launched by default.
If the Intel® Debugger is installed and in your path, you can launch the GUI or command-line version by setting the environment variable INSPXE_DEBUGGER to idb or idbc.
This is low cost for memory error analysis, but can be high cost for threading error analysis.
The debugger is not supported for the mi1 analysis type.
Perform a Locate Memory Problems analysis and connect to the debugger only when an application error is detected.
$ inspxe-cl -collect mi3 -appdebug on-error -- ./test_memory.gcc