Cppcheck is a static analysis tool for C and C++ code. It looks for bugs such as undefined behavior, memory leaks, buffer overruns, null pointer dereferences and uninitialized variables, and it points out code that is suspicious, slow or hard to maintain. Cppcheck tries hard to avoid false positives: when it reports something there is usually a reason to look at it.
The Cppcheck GUI is a graphical front end for Cppcheck. With the GUI you can:
compile_commands.json) and Borland C++ Builder 6 projects,
| Page | What you will find there |
|---|---|
| Getting started | A step by step walk through: create a project, run the analysis and look at the first results. Start here if you are new to Cppcheck. |
| The main window | All menus, toolbars and panels of the main window. |
| Analyzing without a project | Quick analysis of files and folders, and the settings in the Analyze menu. |
| Project files | Every option in the project file dialog explained in detail. |
| Investigating warnings | How to read the results list, the warning details and the code view, and how to decide if a warning is a real bug. |
| Severities and report types | What error, warning, style, performance, portability and information mean, and how the compliance report types classify warnings. |
| Hiding and suppressing warnings | Temporary hiding, permanent suppressions in the project file, and inline suppressions in the code. |
| Tagging warnings | Categorize warnings with your own tags. |
| Results files, printing and statistics | Save and open results, print reports and view statistics. |
| Scratchpad, library editor and other tools | Tools for trying out code and for describing your own libraries. |
| Preferences | Every option in the preferences dialog. |
| Command line options | How to start the GUI with a project or a results file. |
| Troubleshooting | Answers to common questions and problems. |
There are two ways to use the GUI:
*.cppcheck) stores where your code is, the include paths,
the preprocessor defines, the libraries you use, suppressions, tags and
much more. The analysis is more accurate when Cppcheck knows these
things, and you only configure them once. See
Getting started and
Project files.The Cppcheck manual describes the analysis itself in more detail, including the command line tool, the configuration file format and addons. You can find it at https://cppcheck.sourceforge.io/manual.pdf.
The Cppcheck home page is https://cppcheck.sourceforge.io/. There you can download new versions, read about the checks and report problems.