Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!ucsd!ucbvax!agate!agate!rusty From: rusty@belch.Berkeley.EDU (rusty wright) Newsgroups: comp.unix.ultrix Subject: Re: Will Ultrix free() ever learn to reset brk() to free memory? Message-ID: Date: 30 Oct 90 22:09:52 GMT References: <1990Oct30.061026.26014@watcgl.waterloo.edu> Sender: usenet@agate.berkeley.edu (USENET Administrator) Organization: University of California Berkeley Lines: 10 In-Reply-To: idallen@watcgl.waterloo.edu's message of 30 Oct 90 06:10:26 GMT Notice that (on Ultrix 3.1 at least) the malloc man page says for free: The argument to free is a pointer to a block previously allocated by malloc. This space is made available for further allocation, but its contents are left undisturbed. I think it's historical and has something to do with the way malloc, free, and realloc work/interact. This is also what the man page says for 4.3bsd, so I guess 4.3bsd isn't a "nice Unix system" either.