Many commands accept arguments and flags using the following syntax:

A flag acts as an optional switch and is introduced with a forward slash character. Where a command supports flags, the flags are described as part of the command syntax.

The commands you submit to the debugger must conform to the following rules:

You can execute the commands by entering them in the debugger command-line console or by running debugger script files. Alternatively in Eclipse, you can open the DS-5 Debug perspective where you can use the menus, icons, and toolbars provided or you can enter DS-5 Debugger commands in the Commands view.

You can enter many debugger commands in an abbreviated form. The debugger requires enough letters to uniquely identify the command you enter. Many commands have alternative names, or aliases, that you might find easier to remember. For example, backtrace and where are aliases for the info stack command. Command names and aliases can be abbreviated. For example, info stack can be abbreviated to i s. The syntax definition for each command shows how it can be abbreviated by underlining it for example, info stack.

In the syntax definition of each command:

Do not type square brackets, braces, or the vertical pipe. Replace parameters in italics with the value you want. When you supply more than one parameter, use the separator as shown in the syntax definition for each command. If a parameter is a name that includes spaces, enclose it in double quotation marks.

Descriptive comments can be placed either at the end of a command or on a separate line. You can use the # character to identify a descriptive comment.