|
From: Olly B. <ol...@su...> - 2004-06-16 13:30:58
|
On 2004-06-14, Tom Hughes <th...@cy...> wrote:
> What is does do is have an allocated buffer that contains all the
> pointers that have been passed to putenv. When the program exits that
> buffer is freed and the pointer is lost so it winds up looking like
> the memory given to putenv has been lost, which is has in fact, but
> only for those few milliseconds during program exit.
Couldn't valgrind intercept putenv() and track pointers passed, and not
report them as leaks? There's a slight wrinkle since you want to only
exclude the last pointer passed for a given variable name - so you
really need a parallel structure to that which glibc must have.
Cheers,
Olly
|