XSTEP monitor command The optional "task" parameter specifies which of the system program tasks is to be activated. If any of the program arguments (program, param_list, cycles, or step) are specified, program execution is initiated in the same manner as for the EXECUTE command. Unlike that command, however, the first (executable) program instruction is displayed on the system terminal but is not executed. XSTEP must then be entered again, without any program arguments, to execute that instruction. If all the command arguments are omitted, the following actions are performed: 1. The displayed program instruction is executed 2.
The next instruction to be executed is displayed on the system terminal 3. The program is again stopped As with the PROCEED and RETRY commands, an XSTEP command with no arguments can be executed only after execution has stopped due to one of the following events: l An ABORT command or instruction is processed l Single-step execution of the preceding program instruction l A PAUSE instruction is executed l A breakpoint or watchpoint is encountered l Occurrence of a nonfatal error during program execution Examples Initiate execution of program "pack" for three cycles as task 0. The parameters "p2" and "17" are passed to the program.
The first (executable) step of "pack" is displayed in anticipation of its execution with a subsequent XSTEP command (without parameters). XSTEP pack(p2,17),3 Prepare the program "assembly" for execution as program task 0 (or the current debug task) starting at step number 23. If "XSTEP" is then typed, step 23 would be executed. XSTEP assembly,,23 Execute the next step of the program executing as program task 2. XSTEP 2 Execute the next step of the program that was executing as task 0 (or the current debug task). XSTEP Move the execution pointer to step number 45 in the program that was executing as task 0 (or the current debug task).
XSTEP ,,45 eV+Operating System Reference Guide, 2.x,18321-000 Rev A Page 193