System and method for repeating program flow for debugging and testing

• US 8,473,919 B2
• Filed: 01/31/2008
• Issued: 06/25/2013
• Est. Priority Date: 01/31/2008
• Status: Active Grant

• Current Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Original Assignee: CA, Inc. (d/b/a CA Technologies) (Broadcom, Inc.)
• Inventors: Cutler, James Robert
• Primary Examiner(s): Dao, Thuy
• Assistant Examiner(s): Luu, Cuong V
• Application Number:
  US12/023,850
• Publication Number:
  US 20090199161A1
• Time in Patent Office: 1,972 Days
• Field of Search: None
• US Class Current: 717/128
• CPC Class Codes: G06F 11/366 using diagnostics G06F11/0703 takes precedence

Abstract

A method for repeating program flow for debugging and testing purposes comprises storing function call data in one or more files and retrieving the recorded data from the one or more files. The method further comprises using the recorded data to recreate an execution path of a program. Additionally, the method comprises analyzing the execution path to determine a source of an error in the program.

Claims

1. A method executable by a processor, comprising:

storing function call data in one or more files by serializing the function call data;

retrieving the stored function call data from the one or more files by deserializing the function call data;

recreating an execution path of a program using the function call data; and

analyzing the execution path to determine a source of an error in the program, and

parsing the program with a script to identify a function associated with the function call data and, in response to identifying the function, inserting code at an entry point and at an exit point of the function to enable record and replay of inputs and outputs of the function.

2. The method of claim 1, wherein storing function call data is automatically triggered when an error is generated by a function call in the program.

3. The method of claim 1, wherein the function call data comprises function call inputs and reference parameters.

4. The method of claim 1, wherein analyzing the execution path comprises using a debugger.

5. The method of claim 1, further comprising altering code in the program to correct the error in the program.

6. The method of claim 5, further comprising testing the altered code using the recorded data.

7. A system, comprising:

an interface;

a processor;

a storage device embodying a program of instructions operable, when executed on the processor to;

store function call data in one or more files by serializing the function call data;

retrieve the stored function call data from the one or more files by deserializing the function call data;

recreate an execution path of a program using the function call data; and

analyze the execution path to determine a source of an error in the program, and

parse the program with a script to identify a function associated with the function call data and, in response to identifying the function, insert code at an entry point and at an exit point of the function to enable record and replay of inputs and outputs of the function.

8. The system of claim 7, wherein the program of instructions is further operable to automatically store function call data when an error is generated by a function call in the program.

9. The system of claim 7, wherein the function call data comprises function call inputs and reference parameters.

10. The system of claim 7, wherein the program of instructions is further operable to analyze the execution path using a debugger.

11. The system of claim 7, wherein the program of instructions is further operable to alter code in the program to correct the error in the program.

12. The method of claim 11, wherein the program of instructions is further operable to test the altered code using the recorded data.

13. Logic encoded in a non-transitory computer readable medium and operable, when executed on a processor to:

store function call data in one or more files by serializing the function call data;

retrieve the stored function call data from the one or more files by deserializing the function call data;

recreate an execution path of a program using the function call data; and

analyze the execution path to determine a source of an error in the program, and

parse the program with a script to identify a function associated with the function call data and, in response to identifying the function, insert code at an entry point and at an exit point of the function to enable record and replay of inputs and outputs of the function.

14. The logic of claim 13, wherein the logic is further operable to automatically store function call data when an error is generated by a function call in the program.

15. The logic of claim 13, wherein the function call data comprises function call inputs and reference parameters.

16. The logic of claim 13, wherein analyzing the execution path comprises using a debugger.

17. The logic of claim 13, wherein the logic is further operable to alter code in the program to correct the error in the program.

18. The logic of claim 17, the logic is further operable to test the altered code using the recorded data.