Debugging tool and method for tracking code execution paths

• US 20040054991A1
• Filed: 09/17/2002
• Published: 03/18/2004
• Est. Priority Date: 09/17/2002
• Status: Abandoned Application

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: Harres, John M.
• Application Number:
  US10/244,866
• Publication Number:
  US 20040054991A1
• Time in Patent Office: Days
• US Class Current: 717/131
• CPC Class Codes: G06F 11/3664 Environments for testing or debugging software

Abstract

A method for determining code execution paths based on stack information provided in a core file. Stack information is processed to determine flow gaps between pairs of functions identified in frames in the stack. Direct call paths are determined between the functions by determining every direct path between the two functions by scanning the source function for called functions and then repeatedly scanning the called functions until a branch reaches the destination function or terminates with a function other than the destination function. In another embodiment, the paths are determined by identifying call branches from the source function and terminating the following of a call branch whenever a repeat function is found. In another embodiment, the result set of potential paths is generated by identifying branches from the source function but only continuing to follow a branch when intermediate functions are followed by a restore function.

Claims

1. A computer-based method for determining a code execution path, comprising:

retrieving a file including assembly code for functions of a program and data for a stack maintained by a processor running the program, wherein the stack includes frames corresponding to at least some of the functions;

identifying an execution path gap between a first one and a second one of the functions corresponding to a first one and second one of the stack frames; and

determining code execution paths for the gap between the first and second functions.

2. The method of claim 1, wherein the determining includes following function calls from the first to the second function to identify direct call chains and storing the direct call chains as the code execution paths.

3. The method of claim 1, wherein the determining includes identifying branches from the first function beginning with a call to another one of the functions, for each of the identified branches following function calls from the first function to identify direct call chains between the first and the second functions, and storing each of the direct chain branch.

4. The method of claim 3, wherein the following is halted for one of the identified branches upon reaching a function that has been processed previously in the function calls following.

5. The method of claim 1, wherein the determining includes following each function call branch from the first function to the second function by examining each of the functions in the file called until the second function is reached or a terminal leaf in the function call branch is reached.

6. The method of claim 5, wherein the following of a function call branch is continued only when an examined one of the functions is associated with a restore instruction discarding a frame in the stack for the examined one of the functions.

7. The method of claim 6, storing each of the examined function call branch for which the second function is reached during the examining in a set of potential flow paths for the gap in the stack.

8. The method of claim 1, wherein the file is a core file and the program is a kernel for an operating system run by the processor.

9. The method of claim 1, further including repeating the gap identifying and code execution paths determining for additional ones of the functions in adjacent ones of the frames of the stack.

10. The method of claim 1, further including receiving the file from a client computer system and generating a report including at least a portion of the code execution paths.

11. A method for debugging code, comprising:

receiving a core file;

identifying a gap in a code execution path between a source function and a destination function in the core file;

determining call branches from the source function by scanning the source function for all functions called by the source function; and

identifying a set of potential flow paths for the gap by following function calls in each of the call branches that are associated with a restore instruction until a last function in a branch is reached not matching the destination function or the destination function is reached.

12. The method of claim 11, wherein the core file includes assembly code for functions of a kernel of an operating system.

13. The method of claim 11, further including storing the set of potential flow paths and reporting the set of potential flow paths.

14. A computer system for use in debugging code, comprising:

a network interface communicating with a communications network and receiving debugging requests including a core file;

a data storage device for storing the core file; and

a debugger including a mechanism adapted to determine code execution paths between functions in a stack defined in the core file.

15. The system of claim 14, wherein the debugger mechanism determines the code execution paths by identifying execution path gaps between pairs of the functions and for each pair scanning a source one of the pair for called functions and called functions for additional called functions until a destination one of the pair is reached or a terminal function is reached that differs from the destination one.

16. The system of claim 14, wherein the debugger mechanism determines the code execution paths by identifying execution path gaps between pairs of the functions and for each of the pairs having a gap identifying call branches for a source one of the pair and following calls in the branch until a function is reached that has previously been reached in another branch, until a destination one of the pair is reached, or a terminal function is reached differing from the destination one.

17. The system of claim 14, wherein the debugger mechanism determines the code execution paths by identifying execution path gaps between pairs of the functions and for each of the pairs having a gap identifying call branches for a source one of the pair and following calls in the branch for functions included in the core file associated with a restore instruction for the stack until a destination one of the pair is reached or a terminal function is reached differing from the destination one.