#15 some cppcheck reports

[serval24]

Hello,

I runned cppcheck (a free analysis tool) and attached a zip with files, each containing the same kind of warnings.
There may be some false positive (I think about leaks report) but it's quite safe and should be straightforward to fix.

Hope it helps.

Julien.
PS : I couldn't run a full scan (perhaps just a little than half the code), it's very long and I don't know why it's so long (compared for example with LibreOffice sources).

[serval24]

cppcheck reports

[serval24]

Cppcheck about array limits check (I had forgot it)

[Michał Nowakowski]

Thank you for pointing us to this tool. I was able to run it for all the code,
but we need a while before the report can be used, as the code is now
under a little refactoring (Khaled is reducing the number of configuration
directives - I hope cppcheck will run faster as a side effect).

[serval24]

I discovered cppcheck during some contribution to LibreOffice (ie OpenOffice fork).
Cppcheck is very easy and quick to compile so don't hesitate, moreover, cppcheck's authors improve it every day so don't hesitate to use git version.

On LibreOffice, there is now Clang Scan analyzer which could help.
Finally, some devs try to deploy gcov for coverage testing.
2 other tools which may help.