Analyzers
Talk to fellow users of Intel Analyzer tools (Intel VTune™ Profiler, Intel Advisor)
5041 Discussions

How to stop inspxe-cli spawning debugger

Hill__Stephen
Beginner
655 Views

I wish to run inspector from the command-line, enable app-debug=on-error, but stop it spawning a debugger; I just want the GDB server to be run so I can attach to it at my leisure using my debugger of choice.

inspxe-gui allows one from File->Options...->Debugger to choose "Do not automatically start debugger" and I wish to do the same via the cli.

I am guessing there might be a specific string one can set for the environment variable INSPXE_DEBUGGER to do this ... but it is not documented as to what that might be.

0 Kudos
2 Replies
DiyaN_Intel
Moderator
603 Views

Hi, 


Thank you for posting in Intel Communities.


Could you please share the following details so that it helps to understand better and investigate from our end?



1. Complete reproducer code that can be compiled and run to verify behavior.


2. Exact steps and the commands used.


3. OS details.


4. Intel Inspector version.


Thanks and Regards,

Diya


0 Kudos
yuzhang3_intel
Moderator
547 Views

Inspector has one option '-appdebug' below to set debugger behavior. You can also refer to the option description in the user guide.

 

https://www.intel.com/content/www/us/en/docs/inspector/user-guide-linux/2023-2/appdebug.html

 

appdebug

Set when to enable the debugger.

Syntax

-appdebug <value>Argumentsoff

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)DefaultOffActions ModifiedcollectDescriptionUse 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.


Reply