Browse Prior Art Database

Advanced standard output processing within Debugger Disclosure Number: IPCOM000020051D
Original Publication Date: 2003-Oct-21
Included in the Prior Art Database: 2003-Oct-21
Document File: 1 page(s) / 41K

Publishing Venue



This invention remembers the location in the program which was active when output is captured. This position is associated with the output displayed on the screen such that the routine under debug that generated the output can be displayed. The invention also examines output as it is captured and allows the user to break went to the sequence is recognized.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 79% of the total text.

Page 1 of 1

Advanced standard output processing within Debugger

   This invention tracks the position within the program from which output came from. When this output is displayed, its location is remembered. If the user puts the mouse pointer over the output within the debuggers display window, the function which wrote the I/O will be displayed. When the user clicks on a particular piece of output, the user is taken to the location of the program (which is under debug) where the output was written.

     There is also a mechanism for sorting output by the modules where it originated. Because applications can be multi-threaded, output from different modules can be intermingled with each other. Sorting would allow you to see all the output coming from a particular program and service program in the correct order that it was output.

     When debuggers capture this output, they do so by redirecting this output to a socket. To implement this support, the routine (which is called when I/O is written to the socket) simply checks the call stack of the program under debug and remembers the location which wrote the output.

     Another function which is implemented on this trapping of output is the ability to determine when a particular sequence of characters has been written. Once this sequence has been recognized, the program will stop and the user can examine variables. This operation is specified similar to regular breakpoints except that rather than supplying a line #, the user specifies whether...