Scalable omniscient debugging

Pothier, Guillaume; Tanter, Éric; Piquer, José M.

doi:10.1145/1297027.1297067

Cited by 82 publications

(45 citation statements)

References 28 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…However, the root cause of a bug may be not accessible anymore on the call stack when a bug manifest itself [23]. In order to assist the process of finding the root cause of a bug, AODs adopt an event-driven approach and also records the history of turns generated by the application.…”

Section: Statementioning

confidence: 99%

“…Also browsing an event history does not scale since manually inspecting huge traces becomes cumbersome and difficult [3]. As such many research efforts have focused on reducing the amount of events recorded or presented to the user [23,15,44,12]. Nevertheless, event-based debuggers fit well with a non-blocking concurrency model as message sends and receipts can be represented as separate events.…”

Section: Event-based Debugging Toolsmentioning

confidence: 99%

See 1 more Smart Citation

Distributed debugging for mobile networks

Boix

Noguera

Meuter

2014

Journal of Systems and Software

View full text Add to dashboard Cite

Debuggers are an integral part, albeit often neglected, of the development of distributed applications. Ambient-oriented programming (AmOP) is a distributed paradigm for applications running on mobile ad hoc networks. In AmOP the complexity of programming in a distributed setting is married with the network fragility and open topology of mobile applications. To our knowledge, there is no debugging approach that tackles both these issues. In this paper we argue that a novel kind of distributed debugger that we term an ambient-oriented debugger, is required. We present REME-D (read as remedy), an online ambient-oriented debugger that integrates techniques from distributed debugging (event-based debugging, message breakpoints) and proposes facilities to deal with ad hoc, fragile networks -epidemic debugging, and support for frequent disconnections.

show abstract

Section: Statementioning

confidence: 99%

Section: Event-based Debugging Toolsmentioning

confidence: 99%

Distributed debugging for mobile networks

Boix

Noguera

Meuter

2014

Journal of Systems and Software

View full text Add to dashboard Cite

show abstract

“…While the term omniscient debugger has become standard in the literature (Pothier et al 2007;Lewis and Ducassé 2003), it essentially means that the debugger can remember state changes, allowing users to execute code forward and backward. This ability to go backward is critically important in auditory environments.…”

Section: Introductionmentioning

confidence: 99%

Empirical studies on programming language stimuli

Stefik

Gellenbeck

2010

Software Qual J

View full text Add to dashboard Cite

Comprehending and debugging computer programs are inherently difficult tasks. The current approach to building program execution and debugging environments is to use exclusively visual stimuli on programming languages whose syntax and semantics has often been designed without empirical guidance. We present an alternative: Sodbeans, an open-source integrated development environment designed to output carefully chosen spoken auditory cues to supplement empirically evaluated visual stimuli. Originally designed for the blind, earlier work suggested that Sodbeans may benefit sighted programmers as well. We evaluate Sodbeans in two experiments. First, we report on a formal debugging experiment comparing (1) a visual debugger, (2) an auditory debugger, and (3) a multimedia debugger, which includes both visual and auditory stimuli. The results from this study indicate that while auditory debuggers on their own are significantly less effective for sighted users when compared with visual and multimedia debuggers, multimedia debuggers might benefit sighted programmers under certain circumstances. Specifically, we found that while multimedia debuggers do not provide instant usability, once programmers have some practice, their performance in answering comprehension questions improves. Second, we created and evaluated a pilot survey analyzing individual elements in a custom programming language (called HOP) to garner empirical metrics on their comprehensibility. Results showed that some of the most widely used syntax and semantics choices in commercial programming languages are extraordinarily unintuitive for novices. For example, at an aggregate level, the word for, as in a for loop, was rated reliably worse than repeat by more than 673% by novices. After completing our studies, we implemented the HOP programming language and integrated it into Sodbeans.

show abstract

“…A promising direction for alleviating the debugging burden is the use of omniscient debuggers, also known as backin-time or post-mortem debuggers [7,9,10,11]. They record the events that occur during the execution of the debugged program, and then let the user conveniently navigate through the obtained execution trace.…”

Section: Introductionmentioning

confidence: 99%

“…3). We then describe a set of extensions to the TOD open source debugger [11] that greatly enhance the understanding of the dynamics, and therefore the task of debugging, of aspect-oriented programs (Sect. 4).…”

Section: Introductionmentioning

confidence: 99%

Extending omniscient debugging to support aspect-oriented programming

Pothier

Tanter

2008

Proceedings of the 2008 ACM Symposium on Applied Computing

Self Cite

View full text Add to dashboard Cite

Debugging is a tedious and costly process that demands a profound understanding of the dynamic behavior of programs. Debugging aspect-oriented software is even more difficult: to implement the semantics of aspects, a number of implicit activities are performed, whose relation to source code is less direct to grasp. We show how omniscient debugging, a technique that consists in recording the activity of a program to later navigate in its history, can be extended to suit the particularities of aspect-oriented software. By enhancing program understandability, improvements to the tooling associated with aspect orientation will encourage the widespread acceptance of this emerging paradigm.

show abstract

Scalable omniscient debugging

Cited by 82 publications

References 28 publications

Distributed debugging for mobile networks

Distributed debugging for mobile networks

Empirical studies on programming language stimuli

Extending omniscient debugging to support aspect-oriented programming

Contact Info

Product

Resources

About