Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site im4u.UUCP
Path: utzoo!linus!decvax!genrad!panda!talcott!harvard!seismo!ut-sally!im4u!riddle
From: riddle@im4u.UUCP (Prentiss Riddle)
Newsgroups: net.works,net.lang.c
Subject: 4.2 malloc() on Suns?
Message-ID: <514@im4u.UUCP>
Date: Wed, 11-Sep-85 11:38:04 EDT
Article-I.D.: im4u.514
Posted: Wed Sep 11 11:38:04 1985
Date-Received: Sat, 14-Sep-85 03:48:41 EDT
References: <1285@brl-tgr.ARPA> <1506@umcp-cs.UUCP> <5079@allegra.UUCP>
Reply-To: riddle@im4u.UUCP (Prentiss Riddle)
Organization: U. of Tx. at Houston-in-the-Hills
Lines: 16
Xref: linus net.works:877 net.lang.c:5809
Re: malloc(), virtual memory
Maul-Lock: "Bob"

In article <5079@allegra.UUCP> jpl@allegra.UUCP (John P. Linderman) writes:
>
> 		 ...Another ``gotcha''  [in 4.2bsd malloc()]
>to beware of is that space, once allocated, is never broken
>into smaller pieces.  For example, if I allocate a 4 meg
>temporary workspace, free it, then allocate a 2 meg area,
>malloc will not reuse the freed space, it will try for a new
>area, and, thanks to the aforementioned quirks, it will fail
>with the standard 6 meg per-process limit.  Dunno if this is
>fixed under 4.3.

Does anyone know if this has been fixed in the Sun version of malloc()?

--- Prentiss Riddle ("Aprendiz de todo, maestro de nada.")
--- {ihnp4,harvard,seismo,gatech}!ut-sally!riddle   riddle@sally.UTEXAS.EDU
--- Leaving the net soon: friends can write for my new snail-mail address.