46
I Use This!
Very High Activity

News

Analyzed about 11 hours ago. based on code collected about 14 hours ago.
Posted about 15 years ago by [email protected] (Daniel Marjamäki)
There has been various fixes and improvements.Command line: * Now you can specify extra include directories through "-I" * Preliminary xml output through --xml-results. This will be improved further. * The return value of cppcheck is 0 only if no ... [More] errors are found. When errors are found EXIT_FAILURE is returned. * Added support for .C and .c filesNew checks: * sprintf - using overlapping data in input and output * usage of a freed pointer * freeing a pointer that has already been freed * string pointer arithmetic: .. = "abc" 'd'; => .. = "abc" (int)'d'; * mktemp can be dangerousRemoved checks that we think many compilers handle well * unused variable * unreachable code * assignment in conditionImprovements: * Preprocessor macros are handled. (0 comments) [Less]
Posted over 15 years ago by [email protected] (Reijo Tomperi)
We have moved all open feature requests and bug requests to new track ( https://apps.sourceforge.net/trac/cppcheck/report/1 ). If you have any bug reports, feature requests or you would like to submit patches, please use the track.Forums are moved to phpBB, but old posts are not transferred: http://apps.sourceforge.net/phpbb/cppcheck/ (0 comments)
Posted over 15 years ago by [email protected] (Daniel Marjamäki)
Version 1.27 has now been released.A new C check was added that detects when a base class has a non-virtual destructorThe command line options have changed. * --recursive was removed * --errorsonly was renamed to --quiet * --force was ... [More] addedImprovements in the core functionality that makes the checks more accurate.Many small updates in the memory leak checking. (0 comments) [Less]
Posted over 15 years ago by [email protected] (Daniel Marjamäki)
Version 1.26 was released todayIt has many fixes, making the checking both more sensitive and more accurate. In short: * Major restructuring and refactoring were made by Aggro * Buffer overruns: moved recursive checking to "--all" because there ... [More] were false positives * Buffer overruns: fixed false positive (get pointer to data beyond array is not wrong) * Memory leaks: Recursive checking * Memory leaks: Fixed a number of issues in the tracker * Unused functions: new check that is both faster and better than the old one * Class checking: Stronger checking of classes * Resource leaks: check for fopen/popen resource leaksSpecial thanks to kush_eplus for spotting many problems. (0 comments) [Less]
Posted over 15 years ago by [email protected] (Daniel Marjamäki)
Version 1.25 has been released.The GPL 3 license is now used.There has been minor updates. No new checks have been added. Instead the existing checks have been improved. Many false positives have been removed so that the results are now more accurate. (0 comments)
Posted over 15 years ago by [email protected] (Daniel Marjamäki)
A new version has been released.Minor updates in various places. Updated checks: * Unsigned division * Memory leaks * Variable scope * Incomplete statements * Usage of char variables (0 comments)
Posted over 15 years ago by [email protected] (Daniel Marjamäki)
A new version has been released.The checking have been improved.Compilation errors when using DJGPP and GCC-4.3 have been fixed (0 comments)
Posted over 15 years ago by [email protected] (Daniel Marjamäki)
The checking for memory leaks have been restructured and rewritten again.This is the third time I write these checks and this time I hope it will be better.At the moment the check is not that powerful - I have been very focused on avoiding false positives from the start so I have a good and solid ground to build upon in the future. (0 comments)
Posted almost 16 years ago by [email protected] (Daniel Marjamäki)
The cppcheck-1.21 has a few minor updates. (0 comments)
Posted about 16 years ago by [email protected] (Daniel Marjamäki)
Now it's here, the cppcheck-1.20 release.A lot of refactoring to make the code simpler. Simpler code => better code.The checks for memory leaks and buffer overruns have been refactored. (0 comments)