International audienceEfficiently debugging a program requires program comprehension. To acquire it, developers explore the program execution, a task often performed using interactive debuggers. Unfortunately, exploring a program execution through standard interactive debuggers is a tedious and costly task. In this paper, we propose Time-Traveling Queries (TTQs) to ease program exploration. TTQs is a mechanism that automatically explores program executions to collect execution data. This data is used to time-travel through execution states, facilitating the exploration of program executions. We built a set of key TTQs based on typical questions developers ask when trying to understand programs. We conducted a user study with 34 participants...
Debugging is time and energy intensive. Many tools have been developed to help solve the problems as...
Software evolution incurs difficulties in program comprehension and software verification, and hence...
Developers who set a breakpoint a few statements too late or who are trying to diagnose a subtle bug...
International audienceEfficiently debugging a program requires program comprehension. To acquire it,...
International audienceObject-centric debugging aims at facilitating the debugging of object-oriented...
Abstract-We present EXPOSITOR, a new debugging environment that combines scripting and time-travel d...
Compilation-based query engines generate and compile code at runtime, which is then run to get the q...
One reason debugging is the most time-consuming part of software development is because developers s...
Operating systems are difficult to debug with traditional cyclic debugging. They are non-determinist...
We present Expositor, a new debugging environment that combines scripting and time-travel debugging ...
Understanding how a program execution proceeds often helps debug the program. An execution can be se...
AbstractChecking the reliability of software is an ever growing challenge. Fully automatic tools tha...
During debugging, a developer must repeatedly and manu-ally reproduce faulty behaviors in order to i...
Understanding and working with unfamiliar code is often a challenge of software integration or debug...
Abstract — More and more program development tools have turned to Web-based. It has an advantage on ...
Debugging is time and energy intensive. Many tools have been developed to help solve the problems as...
Software evolution incurs difficulties in program comprehension and software verification, and hence...
Developers who set a breakpoint a few statements too late or who are trying to diagnose a subtle bug...
International audienceEfficiently debugging a program requires program comprehension. To acquire it,...
International audienceObject-centric debugging aims at facilitating the debugging of object-oriented...
Abstract-We present EXPOSITOR, a new debugging environment that combines scripting and time-travel d...
Compilation-based query engines generate and compile code at runtime, which is then run to get the q...
One reason debugging is the most time-consuming part of software development is because developers s...
Operating systems are difficult to debug with traditional cyclic debugging. They are non-determinist...
We present Expositor, a new debugging environment that combines scripting and time-travel debugging ...
Understanding how a program execution proceeds often helps debug the program. An execution can be se...
AbstractChecking the reliability of software is an ever growing challenge. Fully automatic tools tha...
During debugging, a developer must repeatedly and manu-ally reproduce faulty behaviors in order to i...
Understanding and working with unfamiliar code is often a challenge of software integration or debug...
Abstract — More and more program development tools have turned to Web-based. It has an advantage on ...
Debugging is time and energy intensive. Many tools have been developed to help solve the problems as...
Software evolution incurs difficulties in program comprehension and software verification, and hence...
Developers who set a breakpoint a few statements too late or who are trying to diagnose a subtle bug...