cppcheck

New checks: * actual initialization order of member variables is not the same as the written order. Use --inconclusive and --enable=style to enable this check. * when first comparison is true, the 2nd comparison is always true. Example: '(x>5 ... [More] && x!=1)'. Use --enable=style to enable this check.we fixed many false positives and false negatives in existing checks.For details, see this list of fixed tickets:http://sourceforge.net/apps/trac/cppcheck/query?status=closed&group=resolution&milestone=1.51 [Less]

New checks: * actual initialization order of member variables is not the same as the written order. Use --inconclusive and --enable=style to enable this check. * when first comparison is true, the 2nd comparison is always true. Example: '(x>5 ... [More] && x!=1)'. Use --enable=style to enable this check. we fixed many false positives and false negatives in existing checks. For details, see this list of fixed tickets: http://sourceforge.net/apps/trac/cppcheck/query?status=closed&group=resolution&milestone=1.51 [Less]

There was many fixes of false positives and serious problems like crashes, hangs, etc.New checks: * Check for std::auto_ptr misuse (related to strict ownership) * Read array and then immediately check if the array index is within limits * assign ... [More] pointer to int/long * assign bool to pointer * duplicate "break" statements in switch * matching "if" and "else if" conditions when using bitwise and * matching assigment and condition when using bitwise and * test if unsigned value is less than zero [Less]

Many bug fixes and improvements.2 more checks were added: * strcmp condition is always true * using sizeof with constant

Release notes for 1.48There are no major new features in 1.48. There are more and better checks.New check: Wrong usage of ! operator in conditions.Example: if (!x == 0) {New check: Use "throw" without arguments to rethrow exceptions. New check: ... [More] Comparison of substring with string literal will always/never match because size doesn't match.New check: Postfix increment of booleanNew check: Clarify condition with parantheses (when there are assignment + comparison)Example: if (a = b > 0) {Total number of tickets fixed : 141More details about all the fixed tickets can be found here:http://sourceforge.net/apps/trac/cppcheck/milestone/1.48 [Less]

Release notes for 1.47It is now possible to exclude files and folders from the analysis. Use -i on the command line (i=ignore).Custom rules can now be created using regular expressions. To read more about creating custom rules, see ... [More] http://sourceforge.net/projects/cppcheck/files/Articles/A new XML format is launched. To use this format, the --xml-version=2 is used. The new xml format is incompatible with the xml format used in previous versions. The old XML format will still be used unless --xml-version=2 is given, so your existing scripts, tools and plugins should still work.New check: sizeof used on array variable that is a function parameter. The expected bahaviour is most likely that the sizeof result is the size of the array, but the actual sizeof result is the size of the pointer.New check: catching exception by value. It is better to catch by reference for various reasons.New check: memset calls filling 0 bytes. The given size might be wrong.Total number of tickets fixed : 174More details about all the fixed tickets can be found here:http://sourceforge.net/apps/trac/cppcheck/milestone/1.47 [Less]

Release notes for 1.46This release has improvements and bug fixes.We fixed 153 tickets, and that is a somewhat "usual" number for a Cppcheck release.The report has been improved. New severities were added to make the messages more informational. The ... [More] possible severities are now: * error * warning * style * performanceThis has no effect on the command line flags nor the xml report. The command line flags and the xml report is fully compatible with previous versions.These are the new checks that were added: * detect dangerous usage of string::c_str() * warn for unused variable when only doing malloc/free * warn when assert has side effects * warn for mutual exclusion over ||. The condition is always false. Example: 'if (x != 1 || x != 4)'More details about all the fixed tickets can be found here:http://sourceforge.net/apps/trac/cppcheck/milestone/1.46 [Less]

GUI: * project fileCommand line: * report: use system dependent path separator * --enable: the except* is not available anymore * --enable: the "unusedFunctions" was renamed to "unusedFunction"Improvements: * New check: Initialization of a variable ... [More] by itself * New check: dangerous usage of scanf * More checking for obsolete and dangerous functions * Optimisations * C++0x updates: enums, stringsDisabled checks: * check that base classes have virtual destructors. Too many false positives currently. * redundant condition before free. Will be possible to enable in the future. * the optional 'exception safety' checks. too many false positivesFixes: * fixed internal errors, segmentation faults, etc * fixed false positives * improved handling when there are internal errors [Less]

I broke out the headers checking into a separate project. Its primary purpose is to detect unnecessary includes.The headers checking was among the first Cppcheck checks. It has been disabled for years because it doesn't work with the Cppcheck ... [More] data.Adapting the Cppcheck data for the headers checking would be complicated and it would involve disabling the Preprocessor - and that is not acceptable. Therefore it was broken out into a separate project.I recommend you download and try checkheaders. The webpage is: http://code.google.com/p/checkheadersThis project is supposed to be compatible with Cppcheck. Existing plugins should be able to execute checkheaders and parse the generated report with minor modifications. [Less]

Interface: * command line: a -D command was added * GUI: minor updatesNew checks: * (style) Redundant assignment (missing break in a switch block) * (style) Empty catch blocks * (error) Usage of iterator pointing to invalid memory after reserve * ... [More] (error) Detect common realloc-mistake that can cause memory leaks.Improved checks: * Memory leaks * Buffer overruns * Mismatching allocation / deallocation * Bad iterators * Uninitialized variables * Null pointer dereference * Unused variable [Less]