Subject: Make's memory (mis)management (was: Re: new vfork(2) implementation)
To: None <thorpej@nas.nasa.gov>
From: None <Havard.Eidnes@runit.sintef.no>
List: current-users
Date: 01/04/1998 21:44:19
> (vfork() makes more of a difference if the process is large in
> terms of address space use, and since make isn't very good
> about managing memory.... :-)

Hm, yes, I've noticed that 'make' can grow pretty large...  It seems
that this is a known fact -- can someone who's looked more than 5
minutes at the code tell me/us a few words about how difficult it
would be to close some (most?) of the leaks (assuming that memory
leaks is indeed the problem)?

- H=E5vard