Table of Contents
Advertisement
Using the 162Bug Debugger
^X
^H
4
Delete
key
^D
^A
^S
^Q
4-2
The presence of the upward caret (
Note
indicates that the Control (CTRL) key must be held
down while striking the character key.
(cancel line)
The cursor is backspaced to the beginning of the line.
(backspace)
The cursor is moved back one position.
(delete)
Performs the same function as ^H.
(redisplay)
The entire command line as entered so far is redisplayed on
the following line.
(repeat)
Repeats the previous line. This happens only at the
command line. The last line entered is redisplayed but not
executed. The cursor is positioned at the end of the line. You
may enter the line as is or you can add more characters to it.
You can edit the line by backspacing and typing over old
characters.
When observing output from any 162Bug command, the XON and
XOFF characters which are in effect for the terminal port may be
entered to control the output, if the XON/XOFF protocol is enabled
(default). These characters are initialized to
by 162Bug, but you may change them with the
initialized (default) mode, operation is as follows:
(wait)
Console output is halted.
(resume)
Console output is resumed.
When a command is entered, the debugger executes the command
and the prompt reappears. However, if the command entered
causes execution of user target code, for example
may or may not return to the debugger, depending on what the
user program does.
For example, if a breakpoint has been specified, then control returns
to the debugger when the breakpoint is encountered during
execution of the user program. Alternately, the user program could
return to the debugger by means of the TRAP #15 ''.RETURN''
function.
) before a character
^
and
respectively
^S
^Q
command. In the
PF
, then control
GO
Advertisement
Table of Contents
