Memory leak in NIS code.

[Cristian Gafton]

On 4 May 1999, Ulrich Drepper wrote:

> > looking into it.  But I don't think I can find all the
> > leaks. Thorsten, could you please double check the NIS code?
> 
> It should be possible to locate the problems with mtrace.

Not exactly, because mtrace does not give me the call stack so I will know
*how* exactly it leaks memory. The fact that mtrace tells me that there is
an insane amount of calls to __strdup that allocates memory that seems to
never be freed tells me nothing about how that leak occurs.

Having mtrace at attempt to walk back at least a couple of call frames
will change radically this situation.

Cristian
--
----------------------------------------------------------------------
Cristian Gafton   --   gafton@redhat.com   --   Red Hat Software, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 UNIX is user friendly. It's just selective about who its friends are.