Debug Manual

Debug Manual—421921-003
D-1
D Session Boundaries
Typically, a Debug session begins when Debug is invoked for a process and the
Debug prompt is displayed on the process’s home terminal. Typically, the session ends
when you leave Debug (EXIT command), resume process execution (R command), or
stop the process (S command). Most Debug commands affect only the current
debugging session. The effects of certain commands, however, cross session
boundaries.
For example if your current Debug session is the result of setting a breakpoint in a
previous session, this current session can inherit options set in the previous session.
The effects of nonprivileged Debug commands can persist as long as the process
being debugged executes. They cannot affect another process.
Privileged commands, however, can affect a whole processor and can persist even if
the particular process being debugged goes away.
The possible scope of Debug commands, both nonprivileged and privileged, is
illustrated in Figure D-1 on page D-2.
Command persistence of nonprivileged commands is summarized in Table D-1. The
table is based on the assumption that you do not issue a command to override or
cancel the particular commands.
Table D-1. Nonprivileged Command Persistence (With Scope of a Process)
Command
Resume
Command
Creates
a New
Process
Process
Stops/Abends
Canceling
Command
BASE Retained Retained * Canceled BASE
B (code breakpoint) Retained Retained * Canceled C
BM (memory-
access breakpoint)
Retained Retained * Canceled CM; inhibited
by a BM ALL
privileged
command
* The commands are retained for the old process. No commands from debugging the old process are inherited
by the new process.