When an exception breakpoint is triggered, execution is suspended
    before any application-declared condition handler is invoked.
    At an exception breakpoint, entering a GO or STEP command after
    executing a routine with the CALL command causes the debugger to
    resignal the exception (see the GO and STEP commands).

    On Alpha processors, you cannot debug routines that are activated
    before the routine activated by a CALL command. For example, your
    program is stopped in routine MAIN, and you set a breakpoint in
    routine SORT. You issue the debugger command CALL SORT. While
    debugging routine SORT, you cannot debug routine MAIN. You must
    first return from the call to routine SO RT.

    If you are debugging a multiprocess program, the CALL command is
    executed in the context of the current process set. In addition,
    when debugging a multiprocess program, the way in which execution
    continues in your process depends on whether you entered a SET
    MODE [NO]INTERRUPT command or a SET MODE [NO]WAIT command. By
    default (SET MODE NOINTERRUPT), when one process stops, the
    debugger takes no action with regard to the other processes.
    Also by default (SET MODE WAIT), the debugger waits until
    all processes in the current process set have stopped before
    prompting for a new command.

    Related commands:

       GO
       EXIT
       SET PROCESS
       SET MODE [NO]INTERRUPT
       STEP