Example: Trace One Instruction Using Debugger; Exception Vector Tables - Motorola MVME167 Series Installation Manual

Example: Trace one instruction using debugger.

167Bug>
PC =00010000 SR
USP =0000DFFC MSP =0000EFFC ISP* =0000FFFC SFC =0=F0
DFC =0=F0
D0 =00000000 D1
D4 =00000000 D5
A0 =00000000 A1
A4 =00000000 A5
00010000 203C0000 0001
167Bug>
PC =00010006 SR
USP =0000DFFC MSP =0000EFFC ISP* =0000FFFC SFC =0=F0
DFC =0=F0
D0 =00000001 D1
D4 =00000000 D5
A0 =00000000 A1
A4 =00000000 A5
00010006 D280
167Bug>

Exception Vector Tables

Notice in the preceding example that the value of the target stack
pointer register (A7) has not changed even though a trace exception
has taken place. Your program may either use the exception vector
table provided by 167Bug or it may create a separate exception
vector table of its own. The two following sections detail these two
methods.
Using 167Bug Target Vector Table
The 167Bug initializes and maintains a vector table area for target
programs. A target program is any program started by the bug:
Preserving the Debugger Operating Environment
RD
=2700=TR:OFF_S._7_..... VBR =00000000
CACR =0=........
=00000000 D2
=00000000 D6
=00000000 A2
=00000000 A6
MOVE.L
T
=2700=TR:OFF_S._7_..... VBR =00000000
CACR =0=........
=00000000 D2
=00000000 D6
=00000000 A2
=00000000 A6
ADD.L
Manually with GO command
Manually with trace commands (T, TC, or TT)
Automatically with the BO command.
=00000000 D3 =00000000
=00000000 D7 =00000000
=00000000 A3 =00000000
=00000000 A7 =0000FFFC
#$1,D0
=00000000 D3 =00000000
=00000000 D7 =00000000
=00000000 A3 =00000000
=00000000 A7 =0000FFFC
D0,D1
5
5-15