#cppcheck

View On WordPress

add_custom_target(cppcheck        WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}        COMMAND /usr/local/bin/cppcheck        --enable=warning,performance,portability,information,missingInclude        --std=c++11        --library=qt.cfg        --template="[{severity}][{id}] {message} {callstack} \(On {file}:{line}\)"        --verbose        --quiet ${SOURCE_FILES}        ) add_custom_target(clangformat        WORKING_DIRECTORY ${PROJECT_SOURCE_DIR}        COMMAND /usr/local/bin/clang-format -style=WebKit -i ${SOURCE_FILES})

hogy a cppcheck nem kiabál, ha nem inicializálsz egy membert. Tök jó, hogy minden szarért pofázik, de a valódi hibákat nem fogja meg. Aztán kitépheted a hajad, mert miafaszér nem megy ez a szar????

I was very glad to see this question: http://stackoverflow.com/questions/31578195/is-there-a-list-of-cppcheck-messages We can be proud of detailed documentation of PVS-Studio.

The author of the peer-to-peer client FlylinkDC++ wrote an article on checking the MatrixSSL project using static code analyzers PVS-Studio and Cppcheck.

Let’s take an example of a memory corruption due to  free of a pointer twice, this cause random crash. It could take few hours or maybe many days to find this kind of issue. Many similar risky problems exist in C/C++ specially concerning memory corruption.  Just one problem could cost few dollars or many thousands of dollars.

New checks: - Compare pointer with '\0' - Assigning boolean expression to floating point variables

We have carried out a thorough comparison of four analyzers for C/C++ code: CppCat, Cppcheck, PVS-Studio and Visual Studio's built-in analyzer. It is a serious, large investigation that we had spent about 170 man-hours on and which, in our opinion, gives a good idea of the general state of things in static analysis nowadays.