Re: hash table memory leak

[J. Grant]

on the 11/03/04 22:52, Paul D. Smith wrote:
> %% "J. Grant" <address@hidden> writes:
>
>   jg> It also makes sense to free ones own memory so that the other
>   jg> memory leaks can be located and fixed.
>
> You have to be careful about what you mean by "memory leaks".  A memory
> leak is some memory which has been allocated on the heap, but the
> pointer to it has been lost (there is no userspace code which can find
> that memory, so it can never be freed by the user).
>
> Memory which is pointed to by some userspace code, so that it _could_ be
> freed, but just happens to not be freed before the process exits, is not
> a memory leak.

Good point.

>   jg> It also makes finding other memory leaks very difficult when there
>   jg> are thousands of individual hash leaks like this...
>
> They're not leaks!! :).

:)

>   jg> Would you reconsider and support a hash table tidy function
>   jg> addition please?
>
> Send it and if it's not too gross I'll add it.

ok, I will submit something soon.


Kind regards

JG