Motorola MVME2700 Series Manuel d'utilisateur Page 63

  • Télécharger
  • Ajouter à mon manuel
  • Imprimer
  • Page
    / 508
  • Table des matières
  • MARQUE LIVRES
  • Noté. / 5. Basé sur avis des utilisateurs
Vue de la page 62
2-1
2
2Using the Debugger
Entering Commands
The debugger is command-driven and performs its various operations in
response to commands that you enter at the keyboard. When the PPCx-
Bug> prompt appears on the screen, the debugger is ready to accept
commands.
What you enter is stored in an internal buffer. Execution begins only after
you press the Return key, allowing you to correct entry errors, if necessary,
using the control characters (refer to Control Characters on page 2-6).
After the debugger executes the command, the prompt reappears.
However, if the command causes execution of target code (for example
GO) then control may or may not return to the debugger, depending on
what the 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. For more about this, refer to the GD,
GO, and GT command descriptions in Chapter 3, Debugger Commands.
Alternately, the user program could return to the debugger by means of the
System Call Handler routine .RETURN (refer to Chapter 5, System Calls).
Command Syntax
A debugger command is made up of the following parts:
The command name
Any required arguments, delineated with either a space or comma
(precede the first argument with a space)
Any required options. Precede an option or a string of options with
a semi-colon (;). If no option is selected, the default options are
used.
Command entry is either uppercase or lowercase.
Vue de la page 62
1 2 ... 58 59 60 61 62 63 64 65 66 67 68 ... 507 508

Commentaires sur ces manuels

Pas de commentaire