Library /sys$common/syshlp/dbg$help.hlb
DEBUG, Language Support, BASIC, Stepping into Routines

 *Conan The Librarian (sorry for the slow response - running on an old VAX)

    The STEP/INTO command is useful for examining external functions.
    However, if you use this command to stop execution at an internal
    subroutine or a DEF, the debugger initially steps into run-time
    library (RTL) routines, providing you with no useful information.
    In the following example, execution is paused at line 8, at a
    call to Print_routine:

         . . .
    ->  8  GOSUB Print_routine
        9  STOP
         . . .
       20  Print_routine:
       21    IF Competition = Done
       22      THEN PRINT "The winning ticket is #";Winning_ticket
       23      ELSE PRINT "The game goes on."
       24    END IF
       25  RETURN

    A STEP/INTO command would cause the debugger to step into the
    relevant RTL code and would inform you that no source lines
    are available for display. On the other hand, a STEP command
    alone would cause the debugger to proceed directly to source
    line 9, past the call to Print_routine. To examine the source
    code of subroutines or DEF functions, set a breakpoint on the
    routine label (for example, enter the SET BREAK PRINT_ROUTINE
    command). You can then suspend execution exactly at the start
    of the routine (line 20, in this example) and then step directly
    into the code.
  Close     HLB-list     TLB-list     Help  

[legal] [privacy] [GNU] [policy] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.