An Optimized Memory Monitoring for Runtime Assertion Checking of C Programs

Kosmatov, Nikolaï; Petiot, Guillaume; Signoles, Julien

doi:10.1007/978-3-642-40787-1_10

Cited by 28 publications

(24 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…By default, this function stops the program execution with a precise error message if a is 0 (i.e., false) and just continues the execution otherwise. The generated code is linked against a dedicated memory library which can efficiently compute the validity of complex memory-related properties (e.g., use-after-free or initialization of variables) [56,64].…”

Section: E-acslmentioning

confidence: 99%

First international Competition on Runtime Verification: rules, benchmarks, tools, and final results of CRV 2014

Bartocci

Falcone

Bonakdarpour

et al. 2017

Int J Softw Tools Technol Transfer

Self Cite

View full text Add to dashboard Cite

The first international Competition on Runtime Verification (CRV) was held in September 2014, in Toronto, Canada, as a satellite event of the 14th international conference on Runtime Verification (RV'14). The event was organized in three tracks: (1) offline monitoring, (2) online monitoring of C programs, and (3) online monitoring of Java programs. In this paper, we report on the phases and rules, a description of the participating teams and their submitted benchmark, the (full) results, as well as the lessons learned from the competition.

show abstract

Section: E-acslmentioning

confidence: 99%

First international Competition on Runtime Verification: rules, benchmarks, tools, and final results of CRV 2014

Bartocci

Falcone

Bonakdarpour

et al. 2017

Int J Softw Tools Technol Transfer

Self Cite

View full text Add to dashboard Cite

show abstract

“…Finally, [21] reports on recent promising work and gives a good overview of previous efforts. The two main other approaches are manual instrumentation and code rewriting (as done by E-ACSL [43] and RiTHM [51]). For C programs it is more common to take changes in variable values as events.…”

Section: Instrumentation Techniquesmentioning

confidence: 99%

What Is a Trace? A Runtime Verification Perspective

Reger

Havelund

2016

Leveraging Applications of Formal Methods, Verification and Validation: Discussion, Dissemination, Applications

View full text Add to dashboard Cite

Abstract. Runtime Monitoring or Verification deals with traces. In its most simple form a monitoring system takes a trace produced by a system and a specification of correct behaviour and checks if the trace conforms to the specification. More complex applications may introduce notions of feedback and reaction. The notion that unifies the field is that we can abstract the runtime behaviour of a system by an execution trace and check this for conformance. However, there is little uniform understanding of what a trace is. This is most keenly seen when comparing theoretical and practical work. This paper surveys the different notions of trace and reflects on the related issues.

show abstract

“…Over the past several years E-ACSL has been experimentally evaluated and used in a number of case studies involving runtime verification of benchmarked and industrial-strength code [15,13,4,2,21,29,28]. This section now briefly summarizes the results of these experiments.…”

Section: Practical Runtime Verification With E-acslmentioning

confidence: 99%

“…Before program instrumentation, static analysis is performed to safely remove unnecessary memory instrumentation to improve efficiency of the monitor [13]. Memory monitoring in E-ACSL has initially been implemented using a compact prefix tree called patricia trie [15]. The trie stores per-block metadata in its leaves and uses base addresses of memory blocks as keys associated with trie nodes.…”

Section: Runtime Detection Of Memory Errorsmentioning

confidence: 99%

“…Initial experiments that involved checking memory-related annotations in a number of small programs (see [15]) indicated that results produced by E-ACSL are precise. Yet, due to complexity of trie lookups, even in small code samples such an approach is prone to producing high runtime overheads of over 100 times compared to performance of unmonitored programs [13].…”

Section: Runtime Detection Of Memory Errorsmentioning

confidence: 99%

See 1 more Smart Citation

E-ACSL, a Runtime Verification Tool for Safety and Security of C Programs (tool paper)

Signoles

Kosmatov

Vorobyov³

Kalpa Publications in Computing

Self Cite

View full text Add to dashboard Cite

This tool paper presents E-ACSL, a runtime verification tool for C programs capable of checking a broad range of safety and security properties expressed using a formal specification language. E-ACSL consumes a C program annotated with formal specifications and generates a new C program that behaves similarly to the original if the formal properties are satisfied, or aborts its execution whenever a property does not hold. This paper presents an overview of E-ACSL and its specification language.

show abstract

An Optimized Memory Monitoring for Runtime Assertion Checking of C Programs

Cited by 28 publications

References 16 publications

First international Competition on Runtime Verification: rules, benchmarks, tools, and final results of CRV 2014

First international Competition on Runtime Verification: rules, benchmarks, tools, and final results of CRV 2014

What Is a Trace? A Runtime Verification Perspective

E-ACSL, a Runtime Verification Tool for Safety and Security of C Programs (tool paper)

Contact Info

Product

Resources

About