Skip to content


Subversion checkout URL

You can clone with
Download ZIP
Tree: 5396b42ca2
Fetching contributors…

Cannot retrieve contributors at this time

36 lines (35 sloc) 1.38 KB
.TH ovs\-parse\-leaks 8 "August 2010" "Open vSwitch" "Open vSwitch Manual"
ovs\-parse\-leaks \- parses OVS leak checker log files
\fBovs\-parse\-leaks\fR [\fIbinary\fR] \fB< \fIlog\fR
Many Open vSwitch daemons accept a \fB\-\-check\-leaks\fR option that
writes information about memory allocation and deallocation to a log
file. \fBovs\-parse\-leaks\fR 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
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.
Prints a usage message and exits.
The output can be hard to interpret, especially for a daemon that does
not exit in normal operation. Using \fBovs\-appctl\fR(8) to invoke
the \fBexit\fR command that some Open vSwitch daemons support
sometimes helps with this.
\fBovs\-parse\-leaks\fR 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.
Jump to Line
Something went wrong with that request. Please try again.