Specifying Debug Tool commands using RDz Debug Configuration

Access the Debug Configuration by selecting RUN -> Debug Configurations. After selecting this option you are presented with the following view:

On the left side, you will see a list of programs under Incoming Remote Debug Session. Pick the program that you are interested in debugging and for which you want to add Debug Tool commands. For this example CICK511 is selected.

Select the Debug Console Commands tab.

The top section labeled as Startup Commands is where you specify the Debug Tool commands that are to be executed at the start of the Debug Tool session.

All commands that you can execute in the Debug Console Commands can also be specified as Startup commands. The only two commands that you can only specify as Startup commands are STEP and GO.

You can specify more than one command separated by a semicolon (;). If you specify STEP or GO, all the commands that follow are not executed, and Debug Tool returns back to the application in STEP or GO mode.

In the following example, three commands are specified: CALL %VER; QUERY LOCATION; GO;

All three commands are executed and because of the GO at the end Debug Tool runs back to the application until a breakpoint is found, a condition is raised, or the application terminates.

In the following example, the order of the commands is changed to CALL %VER; GO; QUERY LOCATION. In this example, the command QUERY LOCATION is not executed because the GO command tells Debug Tool to return to the application.