Micah Cowan <[EMAIL PROTECTED]> writes:
>> Note that, technically, those are not leaks in real need of
>> plugging because they get called only once, i.e. they do not
>> accumulate ("leak") unused memory. Of course, it's still a good
>> idea to remove them, if nothing else, then to remove false
>> positives from DEBUG_MALLOC builds.
>
> I love that valgrind distinguishes these from "unreachable" unfreed
> memory.
By the way, now that valgrind exists, it may be time to consider
retiring DEBUG_MALLOC, a venerable hack from pre-valgrind days. I'm
kind of surprised that anyone even uses it. :-)
