Details
Improvement
Closed
Trivial
Description
Thanks very much for the work.
We install the new version of Cppcheck and I've noticed that the plugin misses some rules when tries to import the report generated from our code. I don't know how to see al the rules, so here are the messages the actual version generates:
[WARN] [20:31:56.411] Cannot find the rule missingScanfFormatWidth, skipping violation
[WARN] [20:31:56.427] Cannot find the rule useInitializationList, skipping violation
Activity
I added updated files for this (attachment: cppcheck.xml, default-profile.xml) but I cannot check the results.
The documentation for CppCheck need some improvement but i found the 2 new messages in the source code
<!-- ########### Missing for cppcheck 1.54 ########### -->
<rule>
<key>StlMissingComparison</key>
<configkey>StlMissingComparison</configkey>
<name>Missing bounds check for extra iterator increment in loop</name>
<description>
Missing bounds check for extra iterator increment in loop. The iterator incrementing is suspicious - it is incremented at line 'line-number-1' and then at line 'line-number-2'
The loop might unintentionally skip an element in the container. There is no comparison between these increments to prevent that the iterator is incremented beyond the end.
</description>
</rule>
<rule>
<key>strncatUsage</key>
<configkey>strncatUsage</configkey>
<name>Dangerous usage of strncat</name>
<description>
Dangerous usage of strncat - 3rd parameter is the maximum number of characters to append.
strncat appends at max its 3rd parameter's amount of characters. The safe way to use strncat is to calculate remaining space in the buffer and use it as 3rd parameter.
</description>
</rule>
<!-- ########### New in cppcheck 1.55 ########### -->
<rule>
<key>useInitializationList</key>
<configkey>useInitializationList</configkey>
<name>member variable shall be initialized using constructor</name>
<description>
When an object of a class is created, the constructors of all member variables are called consecutively in the order the variables are declared, even if you don't explicitly write them to the initialization list.
You could avoid assigning 'symbol' a value by passing the value to the constructor in the initialization list.
</description>
</rule>
<rule>
<key>invalidScanfFormatWidth</key>
<configkey>invalidScanfFormatWidth</configkey>
<name>wrong width for scanf parameter</name>
<description>
Width 'parameter' given in format string (no. 'symbol' ) doesn't match destination buffer.
</description>
</rule>
new CppCheck 1.55 messages