Static Analysis of Run-Time Errors in Embedded Critical Parallel C Programs

Loopfrog — loop summarization for static analysis

10.29007/g3fd ◽

2018 ◽

Author(s):

Daniel Kroening ◽

Natasha Sharygina ◽

Stefano Tonetta ◽

Aliaksei Tsitovich ◽

Christoph M. Wintersteiger

Keyword(s):

Model Checking ◽

Static Analysis ◽

Abstract Interpretation ◽

C Programs ◽

Run Time ◽

Fix Point

Loopfrog is a scalable static analyzer for ANSI-C programs, that combines the precision of model checking and the performance of abstract interpretation. In contrast to traditional static analyzers, it does not calculate the abstract ﬁx-point of a program by iterative application of an abstract transformer. Instead, it calculates symbolic abstract transformers for program fragments (e.g., loops) using a loop summarization algorithm. Loopfrog computes abstract transformers starting from the inner-most loops, which results in linear (in the number of the looping constructs) run-time of the sum- marization procedure and which is often considerably smaller than the traditional saturation procedure of abstract interpetation. It also provides “leaping” counterexamples to aid in the diagnosis of errors.

Download Full-text

Static Analysis of Run-Time Errors in Embedded Real-Time Parallel C Programs

Logical Methods in Computer Science ◽

10.2168/lmcs-8(1:26)2012 ◽

2012 ◽

Vol 8 (1) ◽

Cited By ~ 16

Author(s):

Antoine Miné

Keyword(s):

Real Time ◽

Static Analysis ◽

C Programs ◽

Run Time

Download Full-text

Enhancing the Security of C/C++ Programs using Static Analysis

Indian Journal of Science and Technology ◽

10.17485/ijst/2016/v9i44/104031 ◽

2016 ◽

Vol 9 (44) ◽

Author(s):

Subburaj Ramasamy ◽

Anuj Singh ◽

Deepak Singal

Keyword(s):

Static Analysis ◽

C Programs

Download Full-text

A Suite of Monitoring Tools for Erlang

10.29007/7lrd ◽

2018 ◽

Author(s):

Ian Cassar ◽

Adrian Francalanza ◽

Duncan Attard ◽

Luca Aceto ◽

Anna Ingolfsdottir

Keyword(s):

Model Checking ◽

Static Analysis ◽

Concurrent Systems ◽

Runtime Monitoring ◽

State Explosion ◽

Monitoring Techniques ◽

Monitoring Tools ◽

Run Time ◽

Verification Techniques

Ensuring formal correctness for actor-based, concurrent systems is a difficult task, pri- marily because exhaustive, static analysis verification techniques such as model checking quickly run into state-explosion problems. Runtime monitoring techniques such as Run- time 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.

Download Full-text

Detecting Uninitialized Variables in C++ with the Clang Static Analyzer

Acta Cybernetica ◽

10.14232/actacyb.282900 ◽

2020 ◽

Author(s):

Kristóf Umann ◽

Zoltán Porkoláb

Keyword(s):

Software Engineering ◽

Open Source ◽

Programming Languages ◽

Static Analysis ◽

Common Source ◽

Initial Value ◽

Analysis Techniques ◽

Specific Variable ◽

Prototype Tool ◽

Run Time

Uninitialized variables have been a source of errors since the beginning of software engineering. Some programming languages (e.g. Java and Python) will automatically zero-initialize such variables, but others, like C and C++, leave their state undefined. While laying aside initialization in C and C++ might be a performance advantage if an initial value can't be supplied, working with such variables is an undefined behavior, and is a common source of instabilities and crashes. To avoid such errors, whenever meaningful initialization is possible, it should be used. Tools for detecting these errors run time have existed for decades, but those require the problematic code to be executed. Since in many cases the number of possible execution paths are combinatoric, static analysis techniques emerged as an alternative. In this paper, we overview the technique for detecting uninitialized C++ variables using the Clang Static Analyzer, and describe various heuristics to guess whether a specific variable was left in an undefined state intentionally. We implemented a prototype tool based on our idea and successfully tested it on large open source projects.

Download Full-text