46
I Use This!
Very High Activity

News

Analyzed about 14 hours ago. based on code collected 1 day ago.
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
quick release to fix a few bad bugs. (1 comments)
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
quick release to fix a few bad bugs. (1 comments)
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
Version 1.36 has been released. This new version have many bug fixes for false positives, segmentation faults, etc. We have made many improvements to the handling of C/C++ code which means the checks is stronger. (1 comments)
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
Version 1.36 has been released. This new version have many bug fixes for false positives, segmentation faults, etc. We have made many improvements to the handling of C/C++ code which means the checks is stronger. (1 comments)
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
Version 1.36 has been released. This new version have many bug fixes for false positives, segmentation faults, etc. We have made many improvements to the handling of C/C++ code which means the checks is stronger. (1 comments)
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
Version 1.36 has been released. This new version have many bug fixes for false positives, segmentation faults, etc. We have made many improvements to the handling of C/C++ code which means the checks is stronger. (1 comments)
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
cppcheck-1.35 has been released.Changed output: * Renamed the severity "all" to "possible error" * Renamed the severity "all style" to "possible style" * Removed the severity "security"New checks: * invalid deallocation * memory leaks for struct ... [More] members * Using postincrement when preincrement would be betterImproved checks: * dereferencing null pointers * resource leaks * c-style pointer cast * buffer overrun * dereferencing iterator after using eraseFixed false positives: * member variable not initialized in constructor * possible null pointer dereference * memory leak * returning the address of autovariable * missing virtual destructor * don't show "operator= should return something" when it's privateCompilation: * you can use qmake to build cppcheck. it is the recommended cross platform method.Statistics: 107 files changed, 5862 insertions(+), 2046 deletions(-) (0 comments) [Less]
Posted over 14 years ago by [email protected] (Daniel Marjamäki)
cppcheck-1.35 has been released.Changed output: * Renamed the severity "all" to "possible error" * Renamed the severity "all style" to "possible style" * Removed the severity "security"New checks: * invalid deallocation * memory leaks for struct ... [More] members * Using postincrement when preincrement would be betterImproved checks: * dereferencing null pointers * resource leaks * c-style pointer cast * buffer overrun * dereferencing iterator after using eraseFixed false positives: * member variable not initialized in constructor * possible null pointer dereference * memory leak * returning the address of autovariable * missing virtual destructor * don't show "operator= should return something" when it's privateCompilation: * you can use qmake to build cppcheck. it is the recommended cross platform method.Statistics: 107 files changed, 5862 insertions(+), 2046 deletions(-) (0 comments) [Less]
Posted almost 15 years ago by [email protected] (Daniel Marjamäki)
The biggest news is that we now have a GUI.It is Qt based and should therefore build on any platform.For Windows users the GUI is available in the installation program.We have also made many improvements in the checking. (2 comments)
Posted almost 15 years ago by [email protected] (Daniel Marjamäki)
The biggest news is that we now have a GUI.It is Qt based and should therefore build on any platform.For Windows users the GUI is available in the installation program.We have also made many improvements in the checking. (0 comments)