{"id":101563,"date":"2021-10-07T16:22:54","date_gmt":"2021-10-07T14:22:54","guid":{"rendered":"https:\/\/prohoster.info\/blog\/novosti-interneta\/vypusk-cppcheck-2-6-staticheskogo-analizatora-koda-dlya-yazykov-c-i-s"},"modified":"2021-10-07T16:22:54","modified_gmt":"2021-10-07T14:22:54","slug":"vypusk-cppcheck-2-6-staticheskogo-analizatora-koda-dlya-yazykov-c-i-s","status":"publish","type":"post","link":"https:\/\/prohoster.info\/en\/blog\/news\/vypusk-cppcheck-2-6-staticheskogo-analizatora-koda-dlya-yazykov-c-i-s","title":{"rendered":"Release cppcheck 2.6, a static code analyzer for C++ and C languages.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"
A new version of the static code analyzer cppcheck 2.6 has been released, which allows detecting various classes of errors in C and C++ code, including when using non-standard syntax typical for embedded systems. It provides a collection of plugins that ensure integration of cppcheck with various development, continuous integration, and testing systems, as well as capabilities such as checking code for compliance with styling guidelines. Both its own parser and an external parser from Clang can be used for code analysis. It also includes the donate-cpu.py script for providing local resources to perform collaborative code review for Debian packages. The source code of the project is distributed under the GPLv3 license. <\/p>\n
The development of cppcheck focuses on identifying issues related to undefined behavior and the use of constructs that are hazardous from a security perspective. The goal is also to minimize false positives. Among the identified issues are: pointers to nonexistent objects, division by zero, integer overflows, incorrect bit-shift operations, erroneous type conversions, memory-related issues, improper use of STL, dereferencing null pointers, applying checks after actual access to the buffer, buffer overflows, and the use of uninitialized variables. <\/p>\n
In the new version: <\/p>\n
\n
The following checks have been added to the core analyzer:\n
\n
absence of a return statement in the function body;\n
the comparable value is out of the representable range of the type;\n
copy optimization is not applied for return std::move(local);\n
a file cannot be opened simultaneously for reading and writing in different streams; <\/ul>\n
for Unix platforms, support for outputting diagnostic messages in different colors has been added;\n
symbolic analysis for ValueFlow has been added. A simple delta is used to compute the differences between two unknown variables;\n
The rules used for the token list 'define' can also apply to #include;\n
The library tag can now contain the tag, and accordingly, functions like free that can take such containers, such as std::size, std::empty, std::begin, std::end, etc., can specify yield or action for the containers;\n
The library tag can now contain the tag for smart pointers that have unique ownership. A warning is now issued for 'dangling' references to such smart pointers;\n
Fixed issues with handling the parameter \u2014cppcheck-build-dir;\n
htmlreport can now output author information (using git blame);\n
The warnings about variables that are not constant but could be have been expanded;\n
Resolved accumulated bugs and shortcomings in the analyzer. <\/ul>\n