Inspect Manual

Debugging PATHWAY Applications
Inspect Manual—429164-006
5-13
Guidelines for Debugging Servers
After you enter the DEBUG command, the server enters the hold state as soon as it
completes executing the current machine-code instruction. If the server has invoked a
procedure, it will not enter the hold state until the procedure returns control to the
server.
Guidelines for Debugging Servers
Because servers are simply processes, the guidelines for debugging processes apply
to servers as well. For more information, see Guidelines for Debugging a Process on
page 4-10.
Ending the Debugging Session
You can end the debugging session by entering either the EXIT command or the
RESUME * EXIT command. Neither of these commands alters the PATHWAY
environment, so you should enter PATHCOM and restore PATHWAY to the status it
had before you began debugging. This includes such tasks as stopping and deleting
or altering the server.
When you enter the EXIT command, Inspect terminates the Inspect session, but it
leaves the programs that you were debugging in their current states. Consequently,
you should use the EXIT command only after you have cleared all breakpoints in all
programs and resumed execution of any programs in the hold state. The
RESUME * EXIT command performs these cleanup tasks for you.
When you enter the RESUME * EXIT command, Inspect clears all breakpoints from all
programs on the program list and resumes execution of any programs in the hold state.
It then terminates the Inspect session.
If you have paused the command interpreter on the Inspect command terminal, you
might have to press the BREAK key to signal the command interpreter that it should
prompt again.
Debugging User Conversion Routines
A PATHWAY application can modify the TCP's terminal control logic by adding user
conversion routines to the TCP library and then building a new library file for the TCP.
For more information about user conversion routines, see the TS/MP Management
Programming Manual.
Because user conversion routines become part of the TCP's new library file, the TCP
must be configured for Inspect before you can debug the user conversion routines that
you have written. To ensure that the TCP is configured for Inspect, the Inspect
attribute of the TCP's program file, PATHTCP2, is set ON. Consequently, you do not
have to take any special configuration steps to debug user conversion routines.