Difference between revisions of "Static code analysis"
(Describe used static analysis tools) |
(Improve formatting) |
||
| Line 17: | Line 17: | ||
Some OpenVZ bugs were found using cppcheck: {{B|1309}}, {{B|1308}}, {{B|1307}}, {{B|1306}}. | Some OpenVZ bugs were found using cppcheck: {{B|1309}}, {{B|1308}}, {{B|1307}}, {{B|1306}}. | ||
| + | |||
=== Coverity === | === Coverity === | ||
| − | + | [https://scan.coverity.com/projects/457 vzquota] was submitted as project to Coverity services. | |
| + | There are no known bugs found by Coverity though. | ||
Revision as of 15:47, 9 April 2015
This article is a stub. You can help OpenVZ Wiki by expanding it. Static analysis is a technique for finding bugs just by looking at source code without actually running it. That's great, because it can find bugs that are really hard to trigger.
Contents
Tools used to static analysis of OpenVZ components
There are a number of tools which analyze C code and try to detect typical errors. None of these tools is perfect, so using different tools with OpenVZ components will detect more bugs. Be prepared to also get lots of false warnings!
cppcheck
Cppcheck is a static analysis tool for C/C++ code. Unlike C/C++ compilers and many other analysis tools it does not detect syntax errors in the code. Cppcheck primarily detects the types of bugs that the compilers normally do not detect. The goal is to detect only real errors in the code (i.e. have zero false positives).
Some OpenVZ bugs were found using cppcheck: #1309, #1308, #1307, #1306.
Coverity
vzquota was submitted as project to Coverity services. There are no known bugs found by Coverity though.
