Library /sys$common/syshlp/dbg$help.hlb DEBUG, STEP, Description *Conan The Librarian (sorry for the slow response - running on an old VAX) |
The STEP command is one of the four debugger commands that can be used to execute your program (the others are CALL, EXIT, and GO). The behavior of the STEP command depends on the following factors: o The default STEP mode previously established with a SET STEP command, if any o The qualifier specified with the STEP command, if any o The number of step units specified as the parameter to the STEP command, if any If no SET STEP command was previously entered, the debugger takes the following default actions when you enter a STEP command without specifying a qualifier or parameter: 1. Executes a line of source code (the default is STEP/LINE). 2. Reports that execution has completed by issuing a "stepped to . . . " message (the default is STEP/NOSILENT). 3. Displays the line of source code at which execution is suspended (the default is STEP/SOURCE). 4. Issues the prompt. The following qualifiers affect the location to which you step: /BRANCH /CALL /EXCEPTION /INSTRUCTION /INSTRUCTION=(opcode[, . . . ]) (VAX only) /LINE /RETURN /SEMANTIC_EVENT (Alpha only) /VECTOR_INSTRUCTION (VAX only) The following qualifiers affect what output is seen upon completion of a step: /[NO]SILENT /[NO]SOURCE The following qualifiers affect what happens at a routine call: /INTO /[NO]JSB (VAX only) /OVER /[NO]SHARE /[NO]SYSTEM If you plan to enter several STEP commands with the same qualifiers, you can first use the SET STEP command to establish new default qualifiers (for example, SET STEP INTO, NOSYSTEM makes the STEP command behave like STEP/INTO/NOSYSTEM). Then you do not have to use those qualifiers with the STEP command. You can override the current default qualifiers for the duration of a single STEP command by specifying other qualifiers. Use the SHOW STEP command to identify the current STEP defaults.
|