Debug Manual

Debug Commands
Debug Manual—421921-003
4-45
EX[IT] Command
7000000C: 0x349C94B0 0x39F73AB3 0x3B683E90
70000018: 0x3F8E3FCB 0x40814140
This command displays eight RISC instructions:
248,06,024-DN 0x70000, #8 : R
70000000: SYSCALL BEQ k1,s2,0x700006 SLTIU ....
7000000C: ORI gp,a0,0x34B0 XORI s7,t7,0x3AB3 XORI ....
70000018: LUI t6,0x3FCB MTC0 at,8
This command displays the same memory locations as nonsensical TNS instructions:
248,06,024-DN 0x70000, #8 : T
70000000: STAR 4 STAR 4 BOX +162,5
70000006: BAZ -127 COMW 357 LDX G+127,6
7000000C: LDX G+234,6 LDX G+260,6 NSTO S-027
70000012: NSTO G+263,5 NSTO L+150,5 NSTO G+220,7
70000018: NSTO G+016,7 NSTO L-013,7 LOAD G+201
7000001E: LOAD L+100
EX[IT] Command
The EXIT (or EX) command exits a debug session. The form of the EXIT command is:
Considerations
•
You typically enter an EXIT command when you are finished debugging and want
to continue executing the process. When you enter this command, Debug performs
various cleanup functions, including the following:
°
It clears all breakpoints for the current process.
°
It resumes execution of the process.
If you then reenter Debug, the default base for numeric input and output is set back
to the standard base (hexadecimal for TNS/R registers and addresses, octal for
TNS environment registers and addresses).
•
You cannot resume a process that entered Debug either because it received a
nondeferrable signal or because a synchronous trap occurred. A signal is
nondeferrable if it was generated by the system because the process cannot
continue executing the instruction stream. The only traps from which you can
resume are the looptimer trap and the arithmetic overflow trap, provided that the T
and V bits are not both set in the ENV register.
•
If you enter an EXIT command on a nonresumable process, the process is deleted
after Debug exits with the same Guardian Stop message or OSS wait status as
would have been generated had the signal or trap terminated the process without
entering Debug.
EX[IT]