Debug Manual

Debug Commands
Debug Manual—421921-003
4-56
INSPECT Command
Considerations for Switching From Debug to Inspect
•
The Inspect debugger updates its breakpoint list upon being invoked from Debug.
•
Privileged breakpoints are added only if the Inspect debugger has SET PRIV
MODE ON. For this to happen, you must have (1) been in the Inspect debugger
and entered the SET PRIV MODE ON command, (2) invoked Debug, entered the
PRV command, and set breakpoints, and (3) reinvoked the Inspect debugger.
•
Conditional breakpoints set by Debug are always evaluated conditionally,
regardless of whether you are using the Inspect debugger or Debug.
•
The Inspect LIST BREAKPOINTS command lists information about breakpoints set
in Debug. If the breakpoint has attributes not allowed for Inspect breakpoints (for
example, it is a conditional breakpoint that uses a mask), the Inspect debugger
lists the breakpoint type as one of the following:
Code DEBUG
Data DEBUG
The breakpoint description can include this information:
CONDITIONAL ! Conditional Debug breakpoint
ALL PROCESSES ! Applies to all processes
PRIV ! Set by Debug in privileged mode
•
The Inspect debugger does not list Debug breakpoints if the command:
•
Includes the AS COMMANDS option
•
Is the FB command
Considerations for Switching From Inspect to Debug
•
To switch from the Inspect debugger back to Debug, use the SELECT
DEBUGGER DEBUG command.
•
From the Inspect debugger, you can invoke Debug only on object programs that
are in the hold state. You cannot use Debug on Pathway Screen COBOL
programs.
•
Conditional breakpoints that were set by using the Inspect debugger are reported
unconditionally in Debug.
•
If you invoke Debug from within the Inspect debugger and the process being
debugged terminates, control returns to the Inspect debugger. The Inspect session
terminates if there are no other processes being debugged; otherwise, the Inspect
debugger resets the current program and issues a prompt.
Caution. When returning control to the Inspect debugger after you have used Debug to set “all
process” breakpoints in system code and system library spaces, a deadlock can occur if the
Inspect component process DMON calls the procedure in which you set a breakpoint.