No abstract

Overview of Technologies BenchmarkedThe experiment tested tools representing three technologies: static analysis, model checking, and runtime analysis; and compared them to conventional methods. The static analysis tool was the commercial PolySpace C-verifier [5]. This tool analyzes a C program without executing it; it focuses on finding errors that lead to run-time faults such as underflow/overflow, non-initialized variables, null pointer de-referencing, and array bound checking. The model checking tool was Java PathFinder (JPF) [6], which is an explicit-state model checker that works directly on Java code. JPF specializes in finding deadlocks, verifying assertions, and checking temporal logic specifications. J P F explores all possible interleavings in multi-threaded programs. The runtime analysis tools were Java Path Explorer (JPaX) [4] and DBRover [3]. JPaX can infer potential concurrency errors in a multi-threaded program by examination of a single execution trace. Amongst the errors detectable are deadlocks and data races. DBRover supports conformance check of an execution trace against a specification written in metric temporal logic.

No abstract