After upgrade from cppcheck 2.4.1 to 2.5.0 the issues xml file reduced size from 32MB to 2MB for an example solution. In such a big file it is very difficult to identify more closely the kind of differences.
I run the following command:
cppcheck.exe --enable=all --xml --xml-version=2 --output-file="foo.xml" --project=".\foo.sln" --project-configuration="Release VAC 5.3|Win32"
Do I need to add another option to get (at least) the same amount of issues?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In my experience, 2.5 release had some... issues. Maybe you can try again with current head (https://github.com/danmar/cppcheck/actions/workflows/release-windows.yml), and check if the problem persists?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hmm I have the feeling we fixed something in the filtering of messages. Cppcheck checks often report duplicate messages, for instance if two files include the same header and there is some problem in the header. But the intention is that Cppcheck will not report duplicate messages in the output they are supposed to be filtered.
It would be interesting if you can somehow determine if you have lots of duplicates in your 2.4.1 output. Or if you can see some warning in 2.4.1 that is not shown at all in 2.5.
I guess that you do not have cygwin on your computer? for some grep => sed => sort => uniq command..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
After upgrade from cppcheck 2.4.1 to 2.5.0 the issues xml file reduced size from 32MB to 2MB for an example solution. In such a big file it is very difficult to identify more closely the kind of differences.
I run the following command:
cppcheck.exe --enable=all --xml --xml-version=2 --output-file="foo.xml" --project=".\foo.sln" --project-configuration="Release VAC 5.3|Win32"
Do I need to add another option to get (at least) the same amount of issues?
In my experience, 2.5 release had some... issues. Maybe you can try again with current head (https://github.com/danmar/cppcheck/actions/workflows/release-windows.yml), and check if the problem persists?
hmm I have the feeling we fixed something in the filtering of messages. Cppcheck checks often report duplicate messages, for instance if two files include the same header and there is some problem in the header. But the intention is that Cppcheck will not report duplicate messages in the output they are supposed to be filtered.
It would be interesting if you can somehow determine if you have lots of duplicates in your 2.4.1 output. Or if you can see some warning in 2.4.1 that is not shown at all in 2.5.
I guess that you do not have cygwin on your computer? for some grep => sed => sort => uniq command..