Debugging in Character Mode

On a client running in character mode, the debug ProcScript statement causes a Debug command line to be displayed at the bottom of the screen.

The debug command line has the following format:

{Trigger}Module:StatementNumberDebugInfo >

• Trigger—abbreviation of the trigger name, if applicable. See Trigger Name Abbreviations. If the next ProcScript statement is in global ProcScript, no trigger is displayed.
• Module—label of a ProcScript module. If no explicit module label is present, a module number is generated.
• StatementNumber—number of the statement within the module.
• DebugInfo—either the next ProcScript instruction, or the debugger's response to the previous command.
• > Debug prompt. Enter debugger commands after this prompt.

For example:

• {EXEC} Y1:1 > shows that the next instruction to be executed is the first statement executed in a component, where EXEC identifies the exec operation, Y1 the first module in the component, and 1 the first line in the module.
• DO_TEST:7 > shows that the next instruction to be executed is the seventh line in the DO_TEST global ProcScript.