Date: Thu, 16 Dec 93 11:59:12 -0500 From: DJ Delorie To: raney AT metacard DOT com Cc: djgpp AT sun DOT soe DOT clarkson DOT edu Subject: Re: Malloc returns NULL prematurely in 1.11 > Question: Why is it that when you run out of space in /tmp, malloc > returns NULL, even when there is still gobs of RAM left, at least > according to the DV/X memory monitor? Is a complete mirror of the > process being kept on disk, or DV/X just lying about the available > RAM? Use "go32" to determine how much ram *go32* thinks is available. Chances are, if you ran out of swap space, it was because you've already used up all your physical memory.