debian man page for ovs-parse-leaks

Query: ovs-parse-leaks

OS: debian

Section: 8

Format: Original Unix Latex Style Formatted with HTML and a Horizontal Scroll Bar

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)
Related Man Pages
ovs-brcompatd(8) - debian
ovs-appctl(8) - xfree86
ovs-appctl(8) - opensolaris
ovs-brcompatd(8) - freebsd
ovs-tcpundump(1) - centos
Similar Topics in the Unix Linux Community
problem parsing output file
how to parse this file in unix
Ram Usage
Help to create a script to parse log files
Problem with binary file