Supported code and platforms:

Please understand that there are limits of Cppcheck. Cppcheck is rarely wrong about reported errors. But there are

many bugs that it doesn't detect.

In the project settings dialog, the first option you see is "Import project". It is recommended that you use this

feature if you can. Cppcheck can import:

When you have filled out the project settings and click on OK; the Cppcheck analysis will start.

Checking file1.c...

[file1.c:4]: (error) Array 'a[10]' index 10 out of bounds

Normally a program has many source files. And you want to check them all. Cppcheck can check all source files in a directory:

Configuration problems. The recommendation is to only enable these during configuration.

You can import some project files and build configurations into Cppcheck.

</sizeof>

</platform>

If you use `--project` then Cppcheck will use the preprocessor settings from the imported project. Otherwise you'll probably want to configure the include paths, defines, etc.

x = z;

#endif

You can use `-D` to change this. When you use `-D`, cppcheck will by default only check the given configuration and nothing else. This is how compilers work. But you can use `--force` or `--max-configs` to override the number of configurations.

That will mean that X is not defined. Cppcheck will not check what happens when X is defined.

To add an include path, use `-I`, followed by the path.

If you want to filter out certain errors you can suppress these.

cppcheck --suppress=memleak:src/file1.cpp src/

You can create a suppressions file. Example:

// suppress memleak and exceptNew errors in the file src/file1.cpp

memleak:src/file1.cpp

exceptNew:src/file1.cpp

// suppress all uninitvar errors in all files

uninitvar

void f() {

char arr[5];

// cppcheck-suppress arrayIndexOutOfBounds

arr[10] = 0;

}

// cppcheck-suppress arrayIndexOutOfBounds ; some comment

// cppcheck-suppress arrayIndexOutOfBounds // some comment

Cppcheck can generate output in XML format. Use `--xml` to enable this format.

{

*p = 3; // line 3

}

int main()

{

int *p = 0; // line 8

The other lines in the warning are formatted by the --template-location format.

The available specifiers for --template are:

Carriage return

The available specifiers for `--template-location` are:

}

By default Cppcheck will try to check all the configurations. There are 3 important configurations here:

When you run Cppcheck, the output will be something like:

Checking test.c ...

Checking test.c: __GNUC__=1...

If you think Cppcheck is slow and you are using templates, then you should try how it works to remove unused templates.

Python 2.X or 3.X

Rules that you want to disable does not need to have a rule text. Rules that don't have rule text will be suppressed by the addon.

When external libraries are used, such as WinAPI, POSIX, gtk, Qt, etc, Cppcheck doesn't know how the external functions behave. Cppcheck then fails to detect various problems such as leaks, buffer overflows, possible null pointer dereferences, etc. But this can be fixed with configuration files.

:0 => all values that are less or equal to 0 are valid

0: => all values that are greater or equal to 0 are valid

0,2:32 => the value 0 and all values between 2 and 32 are valid

</function>

</def>

Cppcheck doesn't assume that functions always return. Here is an example code:

If a proper const.cfg is provided, the unreachable code is detected:

Checking const.c...

[const.c:7]: (style) Expression is always false because 'else if' condition matches previous condition at line 5.

</container>

</def>

This command generates the help screen:

./cppcheck gui/test.cpp --xml 2> err.xml

htmlreport/cppcheck-htmlreport --file=err.xml --report-dir=test1 --source-dir=.