Citation Context

...currence of fatal errors, a recovery system may merely be able to store detailed diagnosis information for off-line treatment. 5.2.3 Monitor-oriented Programming Monitoring-Oriented Programming (MOP) =-=[18]-=-, proposed by Feng and Rosu, is a software development methodology, in which the developer specifies desired properties using a variety of (freely definable) specification formalisms, along with code ...

Citation Context

...wn in createCut); and the current state of the property monitor for this run, MS. The property monitor can be any program, in particular those generated automatically from specifications, like in MOP =-=[6]-=-. Figure 5 shows a simple example for generating consistent permutations. Figure 5 (A) is an observed execution of a two-thread program. The solid arrow lines are threads, the dotted arrows are depend...

Citation Context

...oring the monitor instance on a field of the bound object. We first sketched an extended technique incorporating handling of multiple variables in [2], and a limited version is implemented in JavaMOP =-=[12, 17]-=-. That implementation, called ‘decentralised indexing’, avoids the need for an expensive analysis by assuming it is permissible to transform the code of the Java standard libraries, and in many applic...

Citation Context

... verification techniques. There are several frameworks for monitoring runtime events, such as method calls, which trigger additional functionality when particular patterns of events occur [23], [24], =-=[25]-=-. These frameworks support patterns that involve multiple objects. Hence, the FSMs generated by our analysis can be combined with these frameworks to search for violations of the specifications. On th...

Citation Context

...CTJ to the extreme and extends ASPECTJ with regular expressions. Data values are handled by annotating state machine states with constraints, and updating these as events are observed. Chen and Roşu =-=[13]-=- implement a range of traditional logics, such as state machines, temporal logic, regular expressions, and grammars, as different plugins in the MOP system. Data (parameters) are handled uniformly in ...

Citation Context

... number of parameter bindings is large. Parametric properties have been receiving growing interest in runtime verification (RV), as shown by the increasing number of RV systems supporting them, e.g., =-=[3, 1, 14, 12, 7, 13, 15, 9, 5, 4]-=-. Most of these techniques tightly couple the handling of parameter bindings with the property checking, yielding monolithic but supposedly efficient monitors. For example, Tracematches [1] extends st...

Citation Context

...sequences for NASA’s LADEE (Lunar Atmosphere and Dust Environment Explorer) mission [1]. A large number of formalisms have been proposed in recent years for supporting trace analysis, see for example =-=[13, 9, 12, 10, 3, 15, 8]-=-. Examples are temporal logics, including past time as well as future time, regular expressions, state machines, context free grammars, real-time logics, and statistics gathering logics. Most have bee...

Citation Context

... (in particular software model checkers [8]) either specifically target these specifications [16] or use them as their primary example. Similarly, dynamic tools, such as runtime monitoring frameworks =-=[6]-=-, often operate over these temporal properties as well. These tools and techniques have advanced significantly in recent years, particularly in the areas of scalability and automation, but they still ...

Citation Context

...n jMiner grams; we also found several tricky bugs in some well-developed open-source programs by monitoring their executions against the mined specifications using the runtime monitoring tool JavaMOP =-=[11]-=-. We selected for discussion some results from our mining experiments, summarized in Table 2. The first column gives the target classes for which we inferred specifications, together with the software...

Citation Context

...isconnecting and reconnecting a connection c, as well as writing data to c. Note that almost all the aspect code is concerned with bookkeeping internal state. This can induce a large runtime overhead =-=[3,8,11,13,20]-=-. The error message at line 17 implements the only functionality that is visible outside the aspect. Note that the aspect prints the error only if both the advice“disconn”and“write”execute on the same...