Method and apparatus for reverse debugging source code using causal analysis

摘要

A method and apparatus for reverse debugging source code using causal analysis is disclosed. The method comprises executing byte-code created from a plurality of lines of source code, wherein the plurality of lines of source code comprise at least one breakpoint; storing execution data after execution of each line of source code in the plurality of lines of source code until execution reaches the at least one breakpoint; performing a code execution analysis using the execution data and the plurality of lines of source code; receiving an input via a graphical user interface (GUI), wherein the input requests specific execution details based on the code execution analysis; and responding via the GUI to the input.

主权项

1. A computer implemented method for providing causal analysis of execution data via a software debugger comprising:
executing byte-code created from a plurality of lines of source code, wherein the plurality of lines of source code comprise at least one breakpoint; identifying, for each executed line of source code in the plurality of lines of source code, one or more variables within the plurality of lines of source code that experience a change due to the execution of the line of source code just executed; storing execution data after execution of each line of source code in the plurality of lines of source code for the identified one or more variables until execution reaches the at least one breakpoint; performing, upon execution reaching the at least one breakpoint, a code execution analysis using the execution data and the plurality of lines of source code by:
determining a history of the identified one or more variables from beginning of the executed byte-code through the at least one breakpoint, the history of the identified one or more variables comprising only lines of code that affect the identified one or more variables; anddetermining an execution flow history comprising the plurality of lines of source code that caused the execution data to arrive at the at least one breakpoint and filtering out all lines of source code that did not affect the execution data to arrive at the at least one breakpoint; receiving an input via a graphical user interface (GUI), wherein the input requests specific execution details based on the history of the identified one or more variables and the execution flow history; and responding via the GUI by providing the specific execution details based on the history of the identified one or more variables from the beginning of the executed byte-code through the at least one breakpoint.