Browse Prior Art Database

Bypass Function for Navigation in a Source-Level Debugger

IP.com Disclosure Number: IPCOM000113366D
Original Publication Date: 1994-Aug-01
Included in the Prior Art Database: 2005-Mar-27
Document File: 2 page(s) / 36K

Publishing Venue

IBM

Related People

Carley, SC: AUTHOR [+4]

Abstract

Among the functions provided by a typical source-level debugger is the ability to navigate through the application, that is, to control the execution of the application. Examples of this type of navigational function are run, single step, and stop. In addition to these typical functions, debuggers typically provide the ability to manually reposition the statement pointer and continue execution from a point in the program chosen explicitly by the user. In this way, the user of the tool can jump around the logic of the program to execute obscure paths, bypass specific statements, and so on.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 88% of the total text.

Bypass Function for Navigation in a Source-Level Debugger

      Among the functions provided by a typical source-level debugger
is the ability to navigate through the application, that is, to
control the execution of the application.  Examples of this type of
navigational function are run, single step, and stop.  In addition to
these typical functions, debuggers typically provide the ability to
manually reposition the statement pointer and continue execution from
a point in the program chosen explicitly by the user.  In this way,
the user of the tool can jump around the logic of the program to
execute obscure paths, bypass specific statements, and so on.

      One desirable navigational function is the ability to bypass a
single statement of the program.  This can be done (as stated) by
manually positioning the statement pointer to the next statement and
continuing.  However, this is inconvenient.

      A function is provided for navigating through the program being
tested which allows the user to skip the statement about to be
executed.  This function is provided directly, that is, through only
one command or instruction to the debugger.

      For the user, this function is useful at any point in the
program when, during the test, a statement is encountered which the
user does not wish to execute.  For example:

o   a CALL to a subroutine which has not yet been written or which is
    not available, or

o   an initialization statement that th...