Data processing: software development – installation – and managem – Software program development tool – Testing or debugging
Reexamination Certificate
2000-06-13
2003-12-02
Zhen, Wei (Department: 2122)
Data processing: software development, installation, and managem
Software program development tool
Testing or debugging
C717S129000, C714S038110
Reexamination Certificate
active
06658649
ABSTRACT:
BACKGROUND OF THE INVENTION
1. Field of the Invention
The present invention relates to computers and computer software. More specifically, the invention is generally related to debugging software.
2. Background of the Related Art
Inherent in any software development technique is the potential for introducing “bugs”. A bug will typically cause unexpected results during the execution of the program. Locating, analyzing, and correcting bugs in a computer program is a process known as “debugging.” Debugging of programs may be done either manually or interactively by a debugging system mediated by a computer system. Manual debugging of a program requires a programmer to manually trace the logic flow of the program and the contents of memory elements, e.g., registers and variables. In the interactive debugging of programs, the program is executed under the control of a monitor program (known as a “debugger”). The debugger is commonly located on and executed by the same computer system on which the program is executed.
Conventional debuggers typically support various operations to assist a computer programmer. Each operation allows the programmer to examine the state of program registers and variables at a given point in the execution of a program. A first operation supported by conventional debuggers is a breakpoint operation. A “breakpoint” is a point in the program where execution of the computer program is stopped so that the state of the program can be examined by a computer programmer. As a result, when a computer program is executed by a debugger, the program executes in a normal fashion until a breakpoint is reached. The debugger then stops execution and displays the results of the computer program to the programmer for analysis.
Most breakpoints supported by conventional debuggers are unconditional, meaning that once such a breakpoint is reached, execution of the program is always halted. Some debuggers also support the use of conditional breakpoints, which only halt execution of a program when a variable used by the program is set to a predetermined value at the time such a breakpoint is reached.
A second operation supported by conventional debuggers is a “step” function. Step functions known in the art include “step through” (also known as “step into”) and “step over” (also known as “skip” and “next”) operations. Step functions permit a computer programmer to process instructions in a computer program at a source file level (i.e., line by line) and at a statement level, and see the results upon completion of each instruction.
Another operation commonly used by programmers debugging code is known as a “run to” operation. “Run to” operations allow a user to execute code until reaching a predetermined point. For example, a first “Run to” operation makes it possible to skip directly to the end of a procedure from a current position in the procedure. A second “run to” operation allows a programmer to determine where execution will be halted according to placement of a cursor.
Typically, step operations, breakpoints and “run to” operations are used together to simplify the debugging process. Specifically, a common debugging operation is to set a breakpoint at the beginning of a desired set of instructions to be analyzed, and then execute the program. Once the breakpoint is reached, the program is halted, and the programmer then steps through the desired set of instructions line by line or statement by statement using the step operation. Alternatively, the programmer may advance to subsequent points in code space using “run to” operations. Consequently, a programmer is able to isolate and analyze a particular set of instructions without having to step through irrelevant portions of a computer program.
Despite the advantages provided by conventional debugging operations, today's programmers often find the need for additional flexibility. For example, it is often desirable to apply step operations to discrete blocks of code. Conventional solutions include using “run to” points and breakpoints in conjunction with step operations in the manner described above. However, these methods becomes exceedingly time-consuming when many separate blocks of code must be stepped through repeatedly. This also approach suffers because breakpoints are active even when the programmer is not interested in stepping, thereby impacting the efficiency of the programmer.
Another solution is to designate a number (N) of statements to step through. This method, offered by many conventional debuggers, is also burdensome to the programmer because the value of N must be calculated for each separate block of code, and N may be different for each time through the block depending on the control flow.
The disadvantages associated with the prior art are even more pronounced when the code being debugged is pre-processed by a code generator. A code generator operates to add code segments to the code being debugged which may be of no interest to a programmer, thereby further reducing the efficiency of the debugging process. Therefore, there is a need for a debugging program adapted to address the problems associated with step operations.
SUMMARY OF THE INVENTION
The present invention generally provides an apparatus, program product, and a method for debugging computer programs that facilitates step operations.
One aspect of the invention provides a method for debugging a target program containing code. The method comprises establishing a region of the code by designating an entry point in the code and an exit point in the code, executing the code, and halting execution of the code at a first executable instruction after the exit point.
Another aspect of the invention provides a signal bearing medium containing code for a program which, when executed by one or more processors, performs the method described above.
Another aspect of the invention provides a computer system comprising a processor, a memory, an input device, a display device and code for a program which, when executed by the processor, performs a method for debugging the code. The method comprises establishing a region of the code by designating an entry point in the code and an exit point in the code, executing the code, and halting execution of the code at a first executable instruction after the exit point.
REFERENCES:
patent: 5446900 (1995-08-01), Kimelman
patent: 6077311 (2000-06-01), Lichtenstein et al.
patent: 6079032 (2000-06-01), Peri
patent: 6126328 (2000-10-01), Mallory et al.
patent: 6158045 (2000-12-01), You
patent: 6405364 (2002-06-01), Bowman-Amuah
patent: 6412106 (2002-06-01), Leask et al.
Biddle et al. Reuse of Debuggers for Visualization of Reuse. ACM. 1999. pp. 92-100.*
Khoshgoftaar et al. Detection of Software Modules with High Debug Code Churn in a Very Large Legacy System. IEEE. 1996. pp. 364-371.*
McDowell et al. Debugging Concurrent Programs. ACM. 1989. pp. 593-622.*
Mukherjea et al. Toward Visual Debugging: Integrating Algorithm Animation Capabilities Within a Source Level Debugger. ACM. 1994. pp. 215-244.*
U.S. patent application Ser. No. 09/255,109 filed Feb. 22, 1999.
Rosenberg, “How Debuggers Work: Algorithms, Data Structures, and Architecture”, Wiley Computer Publishing© 1996, pp. 119-133, 197-204.
Bates Cary Lee
Day Paul Reuben
Santosuosso John Matthew
Moser, Patterson & Sheridan L.L.P.
Zhen Wei
LandOfFree
Method, apparatus and article of manufacture for debugging a... does not yet have a rating. At this time, there are no reviews or comments for this patent.
If you have personal experience with Method, apparatus and article of manufacture for debugging a..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method, apparatus and article of manufacture for debugging a... will most certainly appreciate the feedback.
Profile ID: LFUS-PAI-O-3152974