Library /sys$common/syshlp/dbg$help.hlb DEBUG, SET, STEP, Parameters  *Conan The Librarian (sorry for the slow response - running on an old VAX)

 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, /VECTOR_
    INSTRUCTION, /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).

 JSB

    (VAX only) If INTO is in effect, subsequent STEP commands are
    treated as STEP/INTO/JSB (step into routines called by a JSB
    instruction as well as those called by a CALL instruction). This
    is the default for all languages except DIBOL.

 NOJSB

    (VAX only; Default.) If INTO is in effect, subsequent STEP
    commands are treated as STEP/INTO/NOJSB (step over routines
    called by a JSB instruction, but step into routines called by
    a CALL instruction). This is the default for DIBOL.

 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).

 VECTOR_INSTRUCTION

    (VAX only) On VAX processors, subsequent STEP commands are
    treated as STEP/VECTOR_INSTRUCTION (step to the next vector
    instruction).