cppcheck 1.28 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News cppcheck 1.28 (Default branch)
# 1  
Old 02-03-2009
cppcheck 1.28 (Default branch)

cppcheck is a static C/C++ code analyzer thatchecks for memory leaks, mismatchingallocation-deallocation, buffer overrun, and manymore problems. Its goal is to produce no falsepositives.License: GNU General Public License v3Changes:
Extra include directories can be specified with-I. XML output can be obtained through the--xml-results option. The program returns 0 onlyif no errors found (else EXIT_FAILURE). The .C and.c++ suffixes are now allowed. New checks wereadded against using overlapping data in input andoutput with sprintf, usage of a freed pointer,freeing a pointer that has already been freed, anddangerous use of mktemp. Some checks were removedsince many compilers handle them well: unusedvariables, unreachable code, and assignments inconditional expressions. Preprocessor macros arehandled.Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
ovs-parse-leaks(8)						Open vSwitch Manual						ovs-parse-leaks(8)

NAME
ovs-parse-leaks - parses OVS leak checker log files SYNOPSIS
ovs-parse-leaks [binary] < log DESCRIPTION
Many Open vSwitch daemons accept a --check-leaks option that writes information about memory allocation and deallocation to a log file. ovs-parse-leaks parses log files produced by this option and prints a summary of the results. The most interesting part of the output is a list of memory blocks that were allocated but not freed, which Open vSwitch developers can use to find and fix memory leaks. The log file must be supplied on standard input. The binary that produced the output should be supplied as the sole non-option argument. For best results, the binary should have debug symbols. OPTIONS
--help Prints a usage message and exits. BUGS
The output can be hard to interpret, especially for a daemon that does not exit in normal operation. Using ovs-appctl(8) to invoke the exit command that some Open vSwitch daemons support sometimes helps with this. ovs-parse-leaks usually incorrectly reports one or more ``bad frees of not-allocated address'' errors at the beginning of output. These reflect frees of data that were allocated before the leak checker was turned on during program initialization. Open vSwitch August 2010 ovs-parse-leaks(8)