Re: Problem with libiberty's hash tables

[Jakub Jelinek <jakub at redhat dot com>]

On Fri, Feb 15, 2008 at 09:13:34PM +0100, Paolo Bonzini wrote:
> 
> > The structures left at the end
> >(which correspond to memory leaks) are then displayed to allow the
> >user to fix his leaks. The CPU usage is probably the limiting factor,
> >here, as I want to avoid slowing the program down more than necessary.
> 
> Sure it's faster this way, but what's wrong with valgrind? ;-)

Or when only talking about memory leaks 
MALLOC_TRACE=myapp.log ./myapp args
mtrace ./myapp myapp.log

	Jakub