Cppcheck
| Original author(s) | Daniel Marjamäki |
|---|---|
| Initial release | May 8, 2007 |
| Stable release | 2.14.2[1] 
/ 22 June 2024 |
| Repository | |
| Written in | C++ |
| Operating system | Cross-platform |
| Available in | English, Dutch, Finnish, Swedish, German, Russian, Japanese, Serbian, Spanish, French, Italian, Korean, Chinese |
| Type | Static code analysis |
| License | GNU General Public License |
| Website | cppcheck |
Cppcheck is a static code analysis tool for the C and C++ programming languages. It is a versatile tool that can check non-standard code.[2] The creator and lead developer is Daniel Marjamäki.
Cppcheck is free software under the GNU General Public License.
Features
[edit]Cppcheck supports a wide variety of static checks that may not be covered by the compiler itself. These checks are static analysis checks that can be performed at a source code level. The program is directed towards static analysis checks that are rigorous, rather than heuristic in nature.
Some of the checks that are supported include:
- Automatic variable checking
- Bounds checking for array overruns
- Classes checking (e.g. unused functions, variable initialization and memory duplication)
- Usage of deprecated or superseded functions according to Open Group[3]
- Exception safety checking, for example usage of memory allocation and destructor checks
- Memory leaks, e.g. due to lost scope without deallocation
- Resource leaks, e.g. due to forgetting to close a file handle
- Invalid usage of Standard Template Library functions and idioms
- Dead code elimination using unusedFunction option
- Miscellaneous stylistic and performance errors
As with many analysis programs, there are many unusual cases of programming idioms that may be acceptable in particular target cases or outside of the programmer's scope for source code correction. A study conducted in March 2009 identified several areas where false positives were found by Cppcheck, but did not specify the program version examined.[4] Cppcheck has been identified for use in systems such as CERNs 4DSOFT meta analysis package,[5] for code verification in high energy particle detector readout devices,[6] system monitoring software for radio telescopes[7] as well as in error analysis of large projects, such as OpenOffice.org[8] and the Debian archive.[9]
Development
[edit]The project is actively under development[10] and is actively maintained in different distributions.[11][12] It has found valid bugs in a number of popular projects[13] such as the Linux kernel and MPlayer.[14]
Plugins
[edit]Plugins for the following IDEs or text editors exist[15]
- CLion[16]
- Code::Blocks - integrated.
- CodeLite - integrated.
- Eclipse[17]
- Emacs[18]
- gedit[19]
- Hudson[20]
- Jenkins[21]
- Kate[22]
- KDevelop[23]
- Qt Creator[24]
- Sublime Text[25]
- Visual Studio[26][27][28]
- Yasca[29]
See also
[edit]
References
[edit]- ^ "Release 2.14.2". 22 June 2024. Retrieved 22 July 2024.
- ^ "A Survey of C and C++ Software Tools for Computational Science" (PDF). Science and Technologies Facility Council. Chilbolton, Daresbury, and Rutherford Appleton Laboratories. December 2009. p. 14. Archived from the original (PDF) on 12 March 2012. Retrieved 14 September 2010.
- ^ "System Interfaces". pubs.opengroup.org. Retrieved 2020-09-24.
- ^ "Static Code Analysis For Embedded Systems" (PDF).
- ^ "Dissemination and use of knowledge plan (EU Deliverable DNA2.11" (PDF). 2010. Archived from the original (PDF) on 2013-06-04. Retrieved 2010-09-15.
- ^ "Entwurf und Implementierung eines adaptiven, strahlentoleranten eingebetteten Systems am Beispiel eines Read-Out-Controllers (En: Development and implementation of an adaptive, radiation tolerant embedded system for operation of a Read-Out controller)" (PDF). 2010. Archived from the original (PDF) on 2012-03-11.
- ^ "The Wettzell System Monitoring Concept and First Realizations" (PDF). International VLBI Service for Geodesy & Astrometry. 2010. p. 447.
- ^ "Hunting for vulnerabilities in large software : the OpenOffice suite" (PDF). Archived from the original (PDF) on 2012-09-28. Retrieved 2010-09-15.
- ^ "Introducing the "Debian's Automated Code Analysis" (DACA) project". LWN.net.
- ^ Cppcheck on Github
- ^ Cppcheck on Debian's Package Tracking System
- ^ FreeBSD port
- ^ "List of user reported bugs found by cppcheck".
- ^ "Found Bugs list". SourceForge. Archived from the original on 2013-10-14.
- ^ "SourceForge.net: cppcheck". sourceforge.net. Archived from the original on 2012-07-18.
- ^ "cppcheck plugin for CLion". plugins.jetbrains.com.
- ^ "Cppcheclipse". github.com.
- ^ "Flycheck". github.com.
- ^ "gedit Cppcheck plugin". github.com. Archived from the original on 2012-12-17.
- ^ "Cppcheck Plugin". hudson-ci.org. Archived from the original on 2017-10-26. Retrieved 2010-09-15.
- ^ "Cppcheck Plugin". jenkins-ci.org. 20 May 2022.
- ^ Cullmann, Christoph (2013-02-02). "Kate Project Plugin News – Code Analysis". Kate | Get an Edge in Editing. Retrieved 2016-12-14.
- ^ Funk, Kevin (2016-12-06). "KDevelop's Cppcheck plugin merged into kdevelop.git, will be released with 5.1". Retrieved 2016-12-14.
- ^ "Qt Creator Plug-in Gallery". Qt Wiki.
- ^ "Sublimelinter plugin". github.com.
- ^ "Cppcheck add-in". Visual Studio Marketplace.
- ^ VioletGiraffe. "Homepage cppcheck-vs-addin". GitHub. Retrieved 3 March 2014.
- ^ Srix. "Simple open source static analysis tool for Visual Studio". Archived from the original on 2015-02-10. Retrieved 27 August 2012.
- ^ Scovetta, Michael. "Yasca".