CodeSonar: Checks for MISRA Rules

The MISRA (Motor Industry Software Reliability Association) standard was created to facilitate best practices for the development of safety-critical software in road vehicles.
The MISRA-C:2004, MISRA-C:2012, and MISRA-C++:2008 rules have also been widely accepted in other industries including aerospace, defense, telecom, and medical.
Dr. Paul Anderson, Vice President of Engineering with CodeSecure, is member of the MISRA® committee to collaborate on world-leading best practice guidelines for the safe and secure development of both embedded control systems and standalone software.

CodeSonar simplifies MISRA Compliance

The latest version of the MISRA rules brings substantial improvements from the previous ones.
Rule 1.3 ("There shall be no occurrence of undefined or critical unspecified behavior.") and Directive 4.1 ("Run-time failures shall be minimized.") are of particular importance. A lot of the most serious bugs in C arise from undefined behavior.

Here some of this bugs:

Buffer overruns and underruns
Double close
Invalid pointer direction
Use of uninitialized memory
Data races
Division by zero

MISRA recommends to use an automated static analysis tool to find violations of the standard. CodeSonar is one of the leading tools for static code analysis. It has been designed for checking safety-critical embedded software.
CodeSonar is an advanced tool, which has deep semantic knowledge of the entire program.
We recommend to avoid lightweight static analysis tools. Although they can find syntactic violations, they are generally not capable of finding the deeper defects.