Establishes default qualifiers (/LINE, /INTO, and so on) for the
STEP command.
Format
SET STEP step-default[, . . . ]
1 – Parameters
BRANCH
Subsequent STEP commands are treated as STEP/BRANCH (step to the
next branch instruction).
CALL
Subsequent STEP commands are treated as STEP/CALL (step to the
next call instruction).
EXCEPTION
Subsequent STEP commands are treated as STEP/EXCEPTION (step to
the next exception).
INSTRUCTION
Subsequent STEP commands are treated as STEP/INSTRUCTION (step to
the next instruction).
On VAX processors, you can also specify one or more instructions
(opcode[, . . . ]). The debugger then steps to the next
instruction in the specified list.
On VAX processors, if you specify a vector instruction, do not
include an instruction qualifier (/UNALIGNED_DATA, /MODIFY, /0,
or /1)) with the instruction mnemonic.
INTO
Subsequent STEP commands are treated as STEP/INTO (step into
called routines) rather than STEP/OVER (step over called
routines). When INTO is in effect, you can qualify the types
of routines to step into by using the [NO]JSB, [NO]SHARE,
and [NO]SYSTEM parameters, or by using the STEP/[NO]JSB,
STEP/[NO]SHARE, and STEP/[NO]SYSTEM command/qualifier
combinations (the latter three take effect only for the immediate
STEP command).
LINE
(Default) Subsequent STEP commands are treated as STEP/LINE (step
to the next line).
OVER
(Default) Subsequent STEP commands are treated as STEP/OVER (step
over all called routines) rather than STEP/INTO (step into called
routines).
RETURN
Subsequent STEP commands are treated as STEP/RETURN (step to the
return instruction of the routine that is currently executing-
that is, up to the point just prior to transferring control back
to the calling routine).
SEMANTIC_EVENT
(Alpha only) Subsequent STEP commands are treated as
STEP/SEMANTIC_EVENT (step to the next semantic event).
SHARE
(Default) If INTO is in effect, subsequent STEP commands
are treated as STEP/INTO/SHARE (step into called routines in
shareable images as well as into other called routines).
NOSHARE
If INTO is in effect, subsequent STEP commands are treated as
STEP/INTO/NOSHARE (step over called routines in shareable images,
but step into other routines).
SILENT
Subsequent STEP commands are treated as STEP/SILENT (after a
step, do not display the "stepped to . . . " message or the source
line for the current location).
NOSILENT
(Default) Subsequent STEP commands are treated as STEP/NOSILENT
(after a step, display the "stepped to . . . " message).
SOURCE
(Default) Subsequent STEP commands are treated as STEP/SOURCE
(after a step, display the source line for the current location).
Also, subsequent SET BREAK, SET TRACE, and SET WATCH commands
are treated as SET BREAK/SOURCE, SET TRACE/SOURCE, and SET
WATCH/SOURCE, respectively (at a breakpoint, tracepoint, or
watchpoint, display the source line for the current location).
NOSOURCE
Subsequent STEP commands are treated as STEP/NOSOURCE (after a
step, do not display the source line for the current location).
Also, subsequent SET BREAK, SET TRACE, and SET WATCH commands
are treated as SET BREAK/NOSOURCE, SET TRACE/NOSOURCE, and
SET WATCH/NOSOURCE, respectively (at a breakpoint, tracepoint,
or watchpoint, do not display the source line for the current
location).
SYSTEM
(Default) If INTO is in effect, subsequent STEP commands are
treated as STEP/INTO/SYSTEM (step into called routines in system
space (P1 space) as well as into other called routines).
NOSYSTEM
If INTO is in effect, subsequent STEP commands are treated as
STEP/INTO/NOSYSTEM (step over called routines in system space,
but step into other routines).
2 – Description
The SET STEP command establishes default qualifiers for
subsequent STEP commands. The parameters that you specify in
the SET STEP command have the same names as the qualifiers for
the STEP command. The following parameters affect where the STEP
command suspends execution after a step:
BRANCH
CALL
EXCEPTION
INSTRUCTION
LINE
RETURN
SEMANTIC_EVENT (Alpha only)
The following parameters affect what output is seen when a STEP
command is executed:
[NO]SILENT
[NO]SOURCE
The following parameters affect what happens at a routine call:
INTO
OVER
[NO]SHARE
[NO]SYSTEM
You can override the current STEP defaults for the duration of a
single STEP command by specifying other qualifiers. Use the SHOW
STEP command to identify the current STEP defaults.
Enabling screen mode by pressing PF1-PF3 enters the SET STEP
NOSOURCE command as well as the SET MODE SCREEN command.
Therefore, any display of source code in output and DO displays
that would result from a STEP command or from a breakpoint,
tracepoint, or watchpoint being triggered is suppressed, to
eliminate redundancy with the source display.
Related commands:
SHOW STEP
STEP
3 – Examples
1.DBG> SET STEP INSTRUCTION,NOSOURCE
This command causes the debugger to execute the program to the
next instruction when a STEP command is entered, and not to
display lines of source code with each STEP command.
2.DBG> SET STEP LINE,INTO,NOSYSTEM,NOSHARE
This command causes the debugger to execute the program to
the next line when a STEP command is entered, and to step into
called routines in user space only. The debugger steps over
routines in system space and in shareable images.