2-14
Computer Group Literature Center Web Site
Startup and Operation
2
displayed on the screen. Any breakpoints installed in your code are
removed and the breakpoint table remains intact. Control returns to the
debugger.
Break
Pressing and releasing the <BREAK> key on the terminal keyboard
generates a ‘‘power break’’. Breaks do not produce interrupts. The only
time that breaks are recognized is while characters are being sent or
received by the console port. A break removes any breakpoints in your
code and keeps the breakpoint table intact. If the function was entered
using SYSCALL, Break also takes a snapshot of the machine state. This
machine state is then accessible to you for diagnostic purposes.
In many cases, you may wish to terminate a debugger command before its
completion (for example, during the display of a large block of memory).
Break allows you to terminate the command.
Diagnostic Facilities
The 172Bug package includes a set of hardware diagnostics for testing and
troubleshooting the MVME172P4. To use the diagnostics, switch
directories to the diagnostic directory.
If you are in the debugger directory, you can switch to the diagnostic
directory with the debugger command Switch Directories (SD). The
diagnostic prompt
172-Diag>
appears. Refer to the Debugging Package
for Motorola 68K CISC CPUs User’s Manual for complete descriptions of
the diagnostic routines available and instructions on how to invoke them.
Note that some diagnostics depend on restart defaults that are set up only
in a particular restart mode. The documentation for such diagnostics
includes restart information.
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com