Goanna—A Static Model Checker

Fehnker, Ansgar; Huuck, Ralf; Jayet, P.; Lussenburg, Michel; Rauch, Felix

doi:10.1007/978-3-540-70952-7_20

Cited by 18 publications

(11 citation statements)

References 5 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We use two tools to this end: SATABS [5,10], geared towards safety analysis, and GOANNA [14], geared towards liveness analysis. Given an active device driver and the set of protocols it implements, we use SATABS to check safety rules 1, 3, and 5 and GOANNA to check liveness rules 2 and 4.…”

Section: Verifying Driver Protocolsmentioning

confidence: 99%

Automatic verification of active device drivers

Amani

Chubb

Donaldson

et al. 2014

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

We develop a practical solution to the problem of automatic verification of the interface between device drivers and the operating system. Our solution relies on a combination of improved driver architecture and verification tools. Unlike previous proposals for verification-friendly drivers, our methodology supports drivers written in C and can be implemented in any existing OS. Our Linuxbased evaluation shows that this methodology amplifies the power of existing model checking tools in detecting driver bugs, making it possible to verify properties that are beyond the reach of traditional techniques.

show abstract

Section: Verifying Driver Protocolsmentioning

confidence: 99%

Automatic verification of active device drivers

Amani

Chubb

Donaldson

et al. 2014

SIGOPS Oper. Syst. Rev.

View full text Add to dashboard Cite

show abstract

“…The goal of driver protocol verification is to check whether the driver meets all safety and liveness requirements assuming fair OS behaviour. We use two tools to this end: SATABS [8], geared towards safety analysis, and GOANNA [13], geared towards liveness analysis. These tools provide complementary capabilities that, when combined, enable full verification of many driver protocols.…”

Section: Verifying Driver Protocolsmentioning

confidence: 99%

Automatic Verification of Message-Based Device Drivers

Amani¹,

Chubb

Donaldson

et al. 2012

Electron. Proc. Theor. Comput. Sci.

View full text Add to dashboard Cite

We develop a practical solution to the problem of automatic verification of the interface between device drivers and the OS. Our solution relies on a combination of improved driver architecture and verification tools. It supports drivers written in C and can be implemented in any existing OS, which sets it apart from previous proposals for verification-friendly drivers. Our Linux-based evaluation shows that this methodology amplifies the power of existing verification tools in detecting driver bugs, making it possible to verify properties beyond the reach of traditional techniques

show abstract

“…Other tools such as Astree [37], CodeSurfer/x86 and WPDS++ [7], Coverity Prevent, FlexeLint, Goanna [44,45], Klocwork K7, Metal [54], PolySpace Verifier, PREfix/PREfast [22], and RT-Tester [90,91] use static analysis itself to analyze programs. As static analysis can be applied to very large programs in contrast to model checking, we can use static analysis to annotate the program with information that is used during state space creation to limit the size of the resulting state spaces.…”

Section: Static Analysis In [Mc]squarementioning

confidence: 99%

Model Checking Software

Donaldson¹,

Parker²

2012

Lecture Notes in Computer Science

View full text Add to dashboard Cite

Software of microcontrollers is getting more and more complex. It is mandatory to extensively analyze their software as errors can lead to severe failures or cause high costs. Model checking is a formal method used to verify whether a system satisfies certain properties.This thesis describes a new approach for model checking software for microcontrollers. In this approach, assembly code is used for model checking instead of an intermediate representation such as C code.The development of [mc]square, which is a microcontroller assembly code model checker implementing this approach, is detailed.[mc]square has a modular architecture to cope with the hardware dependency of this approach. The single steps of the model checking process are divided into separate packages. The creation of the states is conducted by a specific simulator, which is the only hardware-dependent package. Within the simulator, the different microcontrollers are modeled accurately.This work describes the modeling of the ATMEL ATmega16 microcontroller and details implemented abstraction techniques, which are used to tackle the stateexplosion problem. These abstraction techniques include lazy interrupt evaluation, lazy stack evaluation, delayed nondeterminism, dead variable reduction, and path reduction. Delayed nondeterminism introduces symbolic states, which represent a set of states, into [mc]square while still explicit model checking techniques are used. Thus, we successfully combined explicit and symbolic model checking techniques.A formal model of the simulator, which we developed to prove the correctness of abstraction techniques, is described. In this work, the formal model is used to show the correctness of delayed nondeterminism.To show the applicability of the approach, two case studies are described. In these case studies, we used programs of different sizes. All these programs were created by students in lab courses, during diploma theses, or in exercises without the intention to use them for model checking.

show abstract

Goanna—A Static Model Checker

Cited by 18 publications

References 5 publications

Automatic verification of active device drivers

Automatic verification of active device drivers

Automatic Verification of Message-Based Device Drivers

Model Checking Software

Contact Info

Product

Resources

About