Distributed debugging for mobile networks

Abstract

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.

Fault analysis of service‐oriented systems: a systematic literature review

“…However, their approached system is quite sensitive to workload changes depending on the size, the volume of bugs and the bug database isolation level. Boix et al have proposed REME‐D [123] an online ambient‐oriented debugger that integrates techniques from distributed debugging (event‐based debugging, message breakpoints) and facilities to deal with ad hoc , fragile networks, epidemic debugging and supports frequent disconnections.…”

“…Network fragility and open topology of mobile application enhance the complexity of programming in any distributed computing. Boix et al [123] have presented an ambient‐oriented debugger named read as a remedy (REME‐D) that integrates techniques to deal with ad hoc , fragile networks and supports frequent disconnections.…”

A Study of Concurrency Bugs and Advanced Development Support for Actor-based Programs

“…We consider that this approach can be useful for detecting message protocol violations. REME-D [27] is an online debugger for distributed communicating event-loop programs written in AmbientTalk [57]. REME-D provides message-oriented debugging techniques such as the state inspection, in which the developer can inspect an actor's mailbox and objects, while the actor is suspended.…”

“…It also supports a catalog of breakpoints, which can be set on asynchronous and future-type messages sent between actors. Like Causeway, REME-D allows inspecting the history of messages that were sent and received when an actor is suspended, also known as causal link browsing [27]. Therefore, we consider debugging techniques provided in REME-D to be helpful for detecting message order violations.…”

“…Gonzalez Boix et al [27] show the actor state in their REME-D debugger. The actor view shows messages that are going to be executed in the actor's mailbox.…”