|Non-Confidential||PDF version||ARM DUI0446Z|
|Home > Running DS-5 Debugger from the operating system command-line or from a script > Overview: Running DS-5 Debugger from the command-line or from a script|
DS-5 Debugger can operate in a command-line only mode, with no graphical user interface.
This is very useful when automating debug and trace activities. By automating a debug session, you can save significant time and avoid repetitive tasks such as stepping through code at source level. This becomes particularly useful when you need to run multiple tests as part of regression testing.
This mode has the advantage of being extremely lightweight and therefore faster. However, by extension, it also lacks the enhancements that a GUI brings when connecting to a target device such as being able to see synchronization between your source code, disassembly, variables, registers, and memory as you step through execution.
If you want, you can drive the operation of DS-5 Debugger with individual commands in an interactive way. However, DS-5 Debugger when used from the command-line, is typically driven from scripts. With DS-5 Debugger, you might first carry out the required debug tasks in the graphical debugger. This generates a record of each debug task, which can then be exported from the History view as a (.ds) script.
You can edit scripts using the Scripts view. Alternatively, a debug script can be written manually using the DS-5 Debugger commands for reference.
DS-5 also supports Jython (.py) scripts which provide more capability than the native DS-5 scripting language. These can be loaded into DS-5 Debugger to automate the debugger to carry out more complex tasks.
See Command-line debugger options for syntax and instructions on how to launch DS-5 Debugger from the command line.