A Suite of Monitoring Tools for Erlang

Abstract

Ensuring formal correctness for actor-based, concurrent systems is a difficult task, primarily because exhaustive, static analysis verification techniques such as model checking quickly run into state-explosion problems. Runtime monitoring techniques such as Runtime Verification and Adaptation circumvent this limitation by verifying the correctness of a program by dynamically analysing its executions. This paper gives an overview of a suite of monitoring tools available for verifying and adapting actor-based Erlang programs.

Two-Phase Dynamic Analysis of Message-Passing Go Programs Based on Vector Clocks

“…In essence, this vector clock corresponds to the vector clock of the earlier receive. Hence, we find that the third send has the vector clock [5,2] and thus the receive happens before the third send.…”

“…Ignoring the vector clock attached to the empty buffer slot would result in the (post) vector clock [5,0] for the third send. This is clearly wrong as then the receive and (third) send appear to be concurrent to each other.…”

“…We assume communications are as follows: (1) with (3), (2) with (5) and (4) with (6). Here is the resulting trace where assume that signal/trace events have already been processed.…”

Better Late Than Never or: Verifying Asynchronous Components at Runtime

“…We intend to asses the merits of our three instrumentation methods in terms of the multi-faceted overhead metrics proposed by [9]. We also plan to extend detectEr to handle sHML specifications where conjunctions and universal modalities can be treated as separate logical constructs [4,3,39,18,17,24,25]. This facilitates the composition of properties via conjunctions, e.g.…”

VyPR2: A Framework for Runtime Verification of Python Web Services

“…To the best of our knowledge, there is no existing work on Runtime Verification of web services. We are also unaware of other (available and maintained) RV tools for Python (there is Nagini [17], but this focuses on static verification) as most either operate offline (on log files) or focus on other languages such as Java [5,7,18] using AspectJ for instrumentation, C [19], or Erlang [20]. Few RV tools consider the instrumentation problem within the tool.…”