Re: valgrind

[<br...@ph...>]

James R. Van Zandt wrote:
> This leakage turned up every time:

This is a leak-by-design of the C library.  It's not really our job to 
worry about it.

getpwnam() is defined to return a pointer to memory that we don't own. 
We *cannot* free it.  We don't even know it was ever malloc()ed in the 
first place.

> We could use getpwnam_r instead, if it is available.

I seriously doubt that getting gnuplot 100% valgrind-clean is a viable 
goal for the foreseeable future.  Until that changes, I'm against making 
such a change just to quiet valgrind.  We've much bigger cats to skin 
than that one.