System Debug Reference Manual (32650-90888)

Chapter 3 55
System Debug Interface Commands and Intrinsics
Debug Command and Intrinsic Descriptions
Notice that the user was not left in Debug after the command string was executed. In order
to be left in Debug, several criteria must first be met:
• The abort did not occur while in system code, and
• The process entered the abort code through a native mode interrupt. Such aborts are
typically caused by arithmetic and code-related traps (see the XARITRAP and
XCODETRAP intrinsics).
Most CM programs fail these checks and are returned to the CI without entering Debug.
The SETDUMP functionality is also accessible programmatically with the SETDUMP and
HPSETDUMP intrinsics. Refer to the following pages for detailed descriptions and examples.
Debug Command and Intrinsic Descriptions
The commands and intrinsics used with the Stackdump system debugger interface are
described on the following pages. The programming examples are written in Pascal. Refer
to the appropriate language manual set for details of calling system intrinsics from other
languages.
:DEBUG Command
PRIVILEGED MODE
Enters Debug from the CI.
Syntax
:DEBUG [ commands ]
Parameters
commands A series of Debug commands to be executed before the Debug prompt is
displayed. The string may be up to 255 characters long. All text on the
command line following :DEBUG is passed unaltered to Debug. Note that
the commands should not be quoted.
Discussion
The :DEBUG command enters Debug directly from the session CI. Optional Debug
commands may be entered on the command line, and they will be executed before the
Debug prompt is displayed.
If the optional commands contain a Debug command that returns the user to the CI, any
further commands are left pending on Debug's command stack. The next time Debug is