LONDON CodePeer has been developed by AdaCore in partnership with SofCheck Inc. to provide a source code analysis tool that detects run-time and logic errors in Ada programs.
Serving as an efficient and accurate code reviewer, CodePeer identifies constructs that are likely to lead to run-time errors such as buffer overflows, and it flags legal but suspect code typical of logic errors.
Adacore (Paris, France) says the tool goes well beyond the capabilities of typical static analysis tools, producing a detailed analysis of each subprogram, including pre- and postconditions. Such an analysis makes it easier to find potential bugs and vulnerabilities early: if the implicit specification deduced by CodePeer does not match the component's requirements, a reviewer is alerted immediately to a likely logic error.
CodePeer can be used both during system development – to prevent errors from being introduced or as part of a systematic code review process to dramatically increase the efficiency of human review – and retrospectively on existing code, to detect and remove latent bugs. It can be used either as a standalone tool or fully integrated into the GNAT Pro Ada development environment. Its performance that can be tuned based on the memory and speed available on the developer's machine, and can efficiently exploit multi-core CPUs. CodePeer can be run on partially complete programs; it does not require stubs or drivers.
CodePeer analyses programs for a wide range of flaws including use of uninitialised data, pointer misuse, buffer overflow, numeric overflow, division by zero, dead code, and concurrency faults (race conditions).
Adacore says these sorts of errors can be difficult and expensive to detect and correct with conventional debugging, but CodePeer identifies them statically, without running the program, and determines not only where the failure could occur, but identifies where the bad values originate, be it within the current subprogram or from some distant subprogram that reached the point of failure through a series of calls.
CodePeer also looks for code that, although syntactically and semantically correct, is performing a suspect computation, such as an assignment to a variable that is never subsequently referenced, or a conditional test that always evaluates to the same true or false value. Internally CodePeer uses static control-flow, data-flow, and value propagation techniques to identify possible errors. It mathematically analyses every line of code without executing the program, considering all combinations of program input across all paths within the program.
It automatically generates both human-readable and machine-readable component specifications in the form of preconditions, postconditions, inputs, outputs, and heap allocations, which along with the error messages can be displayed graphically or as in-line comments in the source code listing to help immediately pinpoint the root cause of any defect.
In a multi-threaded system CodePeer identifies where race conditions might occur. To increase performance and usability it internally maintains a historical error database, which allows it to highlight just the new coding problems and to track trends across multiple analyses. “The technology underlying CodePeer was developed over many years of work on highly optimising compilers,” said Tucker Taft, Founder and CTO of SofCheck (Burlington, Mass.). “But now we are taking all the information the compiler was using internally for its own optimisation purposes, augmenting it with advanced whole-program analyses, and presenting it in a way that allows the programmer to fix their software before it breaks.”
Related links and articles: