
Restarting the System
program that is being debugged. Abort should be used to regain control if the program gets caught in a loop, etc. The target PC and register contents assist you in locating the malfunction.
Pressing and releasing the ABORT switch generates a local board condition that causes:
❏A processor interrupt (if enabled)
❏The target registers (reflecting the machine state at the time the ABORT switch was pressed) display on the screen
❏All breakpoints installed in your code are removed
❏Breakpoint table remains intact
❏Control returns to the debugger
Break
You can generate a ÒBreakÓ by pressing and releasing the BREAK key on the terminal keyboard. Break does not generate an interrupt. The only time break is recognized is when characters are sent or received by the console port. A Break causes:
❏All breakpoints in your code to be removed
❏Breakpoint table to be maintained intact
❏A snapshot to be taken of the machine state if the function was entered using SYSCALL
❏The snapshot is accessible to you for diagnostic purposes
Often it is desirable to terminate a debugger command prior to its completion; for example, during the display of a large block of memory. Break allows you to terminate the command immediately.
B |