Hello,
I’ve encountered a crash with ArSim and I’m having difficulty retrieving a backtrace.
I’ve managed to connect to it using AS and Debugger, but I’m unable to halt the program and generate a backtrace.
Here’s what I see in the Debugger Console:
(gdb) set print raw frame-arguments on
(gdb) set python print-stack full
(gdb) info break
No breakpoints or watchpoints.
(gdb) undisp
Delete all auto-display expressions? (y or n) [answered Y; input not from terminal]
(gdb) c
(waiting gdb) c
Command ‘c’ is not allowed to be entered in command line.
(waiting gdb) kill
Command ‘kill’ is not allowed to be entered in command line.
(waiting gdb) stop
Command ‘stop’ is not allowed to be entered in command line.
(waiting gdb)
Could you guide me on how to halt the program and retrieve a backtrace?
Hi,
most of the common needed functions of the debugger are available via the Automation Studio code editors / user interface, please see the following link as entry point for more information about the user interfaces for setting breakpoints, reading variable values via watch or debugger watch and so on:
https://help.br-automation.com/#/en/4/diagnostics_support%2Fdiagnosis%2Fdebugging%2Fdiagnosis_debugging.html
From the console output it seems that no breakpoints are set yet.
So you have to set at least one breakpoint at a reachable code position, the task will then stop at this position.
Regarding to “Command xxx is not allowed to be entered in command line”: many gdb commands are disabled by default to avoid interference with the user interfaces of the editors and so on.
Please have a look here for more information about:
https://help.br-automation.com/#/en/4/diagnostics_support/diagnosis/debugging/diagnosis_debugging_gdbconsole.html
Best regards!
1 Like