Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> writes:
> Even better, add a valgrind suppressions file for the warnings and
> ignore them. They are "leaks" only in the sense that a static variable
> is a leak, ie not at all.
Yeah, the bottom line here is that valgrind will warn about many things
that are not genuine problems. You need to learn how to judge the tool's
reports. A single allocation that is still reachable at program exit is
almost never a real problem. If it's unreachable, or there's a lot of
instances, it may be worth worrying about.
regards, tom lane