Representing Code History with Development Environment Events

Dias, Martin; Cassou, Damien; Ducasse, Stéphane

doi:10.48550/arxiv.1309.4334

Cited by 1 publication

(2 citation statements)

References 3 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Once the debugging cycle is finished, a commit operation is issued and the changes handler sends a patch with all recorded changes to the Updater (7).…”

Section: :9mentioning

confidence: 99%

See 1 more Smart Citation

Out-Of-Place debugging: a debugging architecture to reduce debugging interference

2018

View full text Add to dashboard Cite

Context Recent studies show that developers spend most of their programming time testing, verifying and debugging software. As applications become more and more complex, developers demand more advanced debugging support to ease the software development process.Inquiry Since the 70's many debugging solutions have been introduced. Amongst them, online debuggers provide good insight on the conditions that led to a bug, allowing inspection and interaction with the variables of the program. However, most of the online debugging solutions introduce debugging interference to the execution of the program, i.e. pauses, latency, and evaluation of code containing side-effects.Approach This paper investigates a novel debugging technique called out-of-place debugging. The goal is to minimize the debugging interference characteristic of online debugging while allowing online remote capabilities. An out-of-place debugger transfers the program execution and application state from the debugged application to the debugger application, each running in a different process.Knowledge On the one hand, out-of-place debugging allows developers to debug applications remotely, overcoming the need of physical access to the machine where the debugged application is running. On the other hand, debugging happens locally on the remote machine avoiding latency. That makes it suitable to be deployed on a distributed system and handle the debugging of several processes running in parallel.Grounding We implemented a concrete out-of-place debugger for the Pharo Smalltalk programming language. We show that our approach is practical by running several benchmarks, comparing our approach with a classic remote online debugger. We show that our prototype debugger outperforms a traditional remote debugger by 1000 times in several scenarios. Moreover, we show that the presence of our debugger does not impact the overall performance of an application.Importance This work combines remote debugging with the debugging experience of a local online debugger. Out-of-place debugging is the first online debugging technique that can minimize debugging interference while debugging a remote application. Yet, it still keeps the benefits of online debugging (e.g., step-by-step execution). This makes the technique suitable for modern applications which are increasingly parallel, distributed and reactive to streams of data from various sources like sensors, UI, network, etc. ACM CCS 2012Software and its engineering → Software testing and debugging;

show abstract

“…Once the debugging cycle is finished, a commit operation is issued and the changes handler sends a patch with all recorded changes to the Updater (7).…”

Section: :9mentioning

confidence: 99%

“…To correctly detect code changes in the debugger project, the IDRA Changes Handler leverages on Epicea [7], an existent library for handling such events.…”

Section: Handling Of Exceptions and Code Changesmentioning

confidence: 99%