Browse Prior Art Database

Graphical Monitoring of an Executing Application

IP.com Disclosure Number: IPCOM000105552D
Original Publication Date: 1993-Aug-01
Included in the Prior Art Database: 2005-Mar-20
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Related People

Borchardt, EK: AUTHOR [+3]

Abstract

Disclosed is the use by a code debugger of a graphical diagram to identify which part of an application is executing. An arrow is used to point into the diagram at the application module that is currently executing. In the Figure, the arrow indicates that GRAPH2 is currently executing. As the module passes control to another module or returns control, the arrow shifts accordingly. The window in the bottom right hand corner of the figure shows what statement in GRAPH2 is executing.

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

Graphical Monitoring of an Executing Application

      Disclosed is the use by a code debugger of a graphical diagram
to identify which part of an application is executing.  An arrow is
used to point into the diagram at the application module that is
currently executing.  In the Figure, the arrow indicates that GRAPH2
is currently executing.  As the module passes control to another
module or returns control, the arrow shifts accordingly.  The window
in the bottom right hand corner of the figure shows what statement in
GRAPH2 is executing.

      Many debuggers provide information as to where an application
is currently executing by displaying the current instruction.
However, the only indication that is usually provided as to the
location of that instruction is the name of the module containing it.
By contrast, the use of a graphical diagram provides a continually
updated "you-are-here" map to the user.  Rather than merely giving
the name of the currently executing module, graphical monitoring
points to it so that it can be seen within the context of an entire
application.