4-14
Using the 162Bug Debugger
4
pointer values just before the exception occurred. In this way, the
operation of the debugger facility (through an exception) is
transparent to users.
Example: Trace one instruction using the debugger firmware.
172-Bug>rd
PC =00010000 SR =2708=TR:OFF_S._7_N.. VBR =00000000
SSP =0000FFFC USP =00010000 SFC =1=UD DFC =1=UD
CACR =00000000=D: ....._B:..._I:... PCR =04310402
D0 =FFFFFFFF D1 =00000000 D2 =00000000 D3 =00000000
D4 =00000000 D5 =00000000 D6 =00000000 D7 =00000000
A0 =00000000 A1 =00000000 A2 =00000000 A3 =00000000
A4 =00000000 A5 =00000000 A6 =00000000 A7 =0000FFFC
IPLR =00000007 IML
R
=00000000 MMIE
N
=00000003 VIEN =C0000000
VIST =00000000 PIEN =00002000 PIST =00000000
00010000 203C0000 0001MOVE.L#$1,D0
172-Bug>t
PC =00010006 SR =2700=TR:OFF_S._7_..... VBR =00000000
SSP* =0000FFFC USP =00010000 SFC =1=UD DFC =1=UD
CACR =00000000=D: ....._B:..._I:... PCR =04310402
D0 =00000001 D1 =00000000 D2 =00000000 D3 =00000000
D4 =00000000 D5 =00000000 D6 =00000000 D7 =00000000
A0 =00000000 A1 =00000000 A2 =00000000 A3 =00000000
A4 =00000000 A5 =00000000 A6 =00000000 A7 =0000FFFC
IPLR =00000007 IML
R
=00000000 MMIE
N
=00000003 VIEN =C0000000
VIST =00000000 PIEN =00002000 PIST =00000000
00010006 D280 0001ADD.LD0,D1
172-Bug>
To Next Page
Loading...
