Debugger General Information
❏Various 177Bug routines that handle I/O, data conversion, and string functions available to user programs through the TRAP #15 system calls
177Bug consists of three parts:
❏A command-driven user-interactive software debugger, described in this appendix, and hereafter referred to as Òthe debuggerÓ or Ò177BugÓ
❏A command-driven diagnostic package for the MVME177 hardware, hereafter referred to as Òthe diagnosticsÓ
❏A user interface which accepts commands from the system console terminal
When using 177Bug, you operate out of either the debugger directory or the diagnostic directory. If you are in the debugger directory, the debugger prompt Ò177-Bug>Ó displays and you have all of the debugger commands at your disposal. If you are in the diagnostic directory, the diagnostic prompt Ò177-Diag>Ó displays and you have all of the diagnostic commands at your disposal as well as all of the debugger commands. You may switch between directories by using the Switch Directories (SD) command, or may examine the commands in the particular directory that you are currently in by using the Help (HE) command.
Because 177Bug is command-driven, it performs its various operations in response to user commands entered at the keyboard. When you enter a command, 177Bug executes the command and the prompt reappears. However, if you enter a command that causes execution of user target code (e.g., ÒGOÓ), then control may or may not return to 177Bug, depending on the outcome of the user program.
If you have used one or more of Motorola's other debugging packages, you will find the CISC 177Bug very similar. Considerable effort has also been made to make the interactive commands more consistent. For example, delimiters between commands and arguments may now be commas or spaces interchangeably.
