Debug Manual

Introduction
Debug Manual—421921-003
1-10
Ending a Debug Session
Ending a Debug Session
Two commands are provided for ending a Debug session: the STOP command and
the EXIT command.
•
The STOP command stops execution of the current process and deletes it.
•
The EXIT command clears all breakpoints and resumes execution of the current
process.
What Appears in the Debug Header Message
When a process enters Debug, regardless of the reason, Debug opens the home
terminal. If Debug cannot open the home terminal, the process stops unless it cannot
stop, in which case, it continues.
When Debug opens the home terminal, it prints a header message on the terminal.
The header message displays the current values of the P or PC and the ENV registers,
the current space identifier, and information as to why your process entered Debug.
These examples illustrate different Debug header messages:
DEBUG P=%001025, E=%000017, UC.%00 ! Gives current values of
101,01,00012- ! TNS environment P and ENV
! registers and space identifier.
DEBUG P=%037175, E=%000017, UC.%03 - TRAP #03 -!Process entered
Debug
099,00,00039- ! when it encountered
! a stack overflow.
Header Message Format
The format of the header message appears in the box below; the element descriptions
follow:
DEBUG {P=P-register, E=ENV-register, space-identifier}[ info
]
{PC=32-bit-address }
sys,cpu,pin [cmd]-