DrDebug

Wang, Yan; Patil, Harish; Pereira, Cristiano; Lueck, Gregory; Gupta, Rajiv; Neamtiu, Iulian

doi:10.1145/2544137.2544152

Cited by 13 publications

(3 citation statements)

References 30 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…", and therefore contributes to solving the challenge of Monitoring Object-Specific Interactions. DrDebug [12] replays deterministically slices of a program execution. The slices are computed depending on a condition that developers have to determine.…”

Section: Object-centric Omniscient Approachesmentioning

confidence: 99%

Scopeo: an Object-Centric Debugging Approach for Exploring Object-Oriented Programs

Bourcier,

Costiou

2024

2024 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)

View full text Add to dashboard Cite

Debugging object-oriented programs requires understanding how objects interact with each other and how their state evolves during execution. It is an arduous activity, as there are no methods to support finding objects to debug and explore their interactions.In this paper we present Scopeo, a novel object-centric approach to explore objects and their interactions in objectoriented programs. We evaluate the performance of Scopeo and conclude its applicability to real debugging scenarios. We then open a discussion on the interest of this approach for future research into debugging and program comprehension.

show abstract

Section: Object-centric Omniscient Approachesmentioning

confidence: 99%

Scopeo: an Object-Centric Debugging Approach for Exploring Object-Oriented Programs

Bourcier,

Costiou

2024

2024 IEEE International Conference on Software Analysis, Evolution and Reengineering (SANER)

View full text Add to dashboard Cite

show abstract

“…Program Slicing: Program slicing finds all possible statements that are relevant to a seed statement or value of interest [Korel and Laski 1988;Musuvathi et al 2008;Sahoo et al 2013;Wang et al 2014;Zhang et al 2003]. Comparing to Watcher, static slicing is imprecise [Harman and Hierons 2001], but it provides more relevant instructions that dynamic slicing cannot do, such as some non-executed instructions in the failing execution.…”

Section: Related Workmentioning

confidence: 99%

WATCHER: in-situ failure diagnosis

Liu

Silvestro

Zhang

et al. 2020

Proc. ACM Program. Lang.

View full text Add to dashboard Cite

Diagnosing software failures is important but notoriously challenging. Existing work either requires extensive manual effort, imposing a serious privacy concern (for in-production systems), or cannot report sufficient information for bug fixes. This paper presents a novel diagnosis system, named Watcher, that can pinpoint root causes of program failures within the failing process ("in-situ"), eliminating the privacy concern. It combines identical record-and-replay, binary analysis, dynamic analysis, and hardware support together to perform the diagnosis without human involvement. It further proposes two optimizations to reduce the diagnosis time and diagnose failures with control flow hijacks. Watcher can be easily deployed, without requiring custom hardware or operating system, program modification, or recompilation. We evaluate Watcher with 24 program failures in real-world deployed software, including large-scale applications, such as Memcached, SQLite, and OpenJPEG. Experimental results show that Watcher can accurately identify the root causes in only a few seconds.CCS Concepts: • Software and its engineering → Software testing and debugging; Dynamic analysis.

show abstract

“…Trace recording is especially challenging in concurrent and distributed systems due to non-determinism. Several replay debuggers exist to overcome these issues with different tradeoffs [14,21,28,34,36]. In order to deal with non-deterministic inputs, a partial order of variable accesses or events has to be stored in the trace to be able to reproduce the program concurrent behaviour.…”

Section: Offline Debuggingmentioning

confidence: 99%

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

DrDebug

Cited by 13 publications

References 30 publications

Scopeo: an Object-Centric Debugging Approach for Exploring Object-Oriented Programs

Scopeo: an Object-Centric Debugging Approach for Exploring Object-Oriented Programs

WATCHER: in-situ failure diagnosis

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

Contact Info

Product

Resources

About