Date: Wed, 9 Jun 1999 11:41:08 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Dlanor Blytkerchan <dlanor AT dds DOT nl>
cc: djgpp AT delorie DOT com
Subject: Re: malloc() problem (resumed)
In-Reply-To: <l03130300b383102c9e18@[145.98.116.75]>
Message-ID: <Pine.SUN.3.91.990609113850.11862L-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Tue, 8 Jun 1999, Dlanor Blytkerchan wrote:

> In response to the suggestion of running go32-v2 from within the program.
> I've done that just now. The error is still the same. go32-v2 reports just
> below 2 MBs of free DPMI memory available, and several MBs of swap space.

Weird.  Please post the shortest program that exhibits this problem on
your system, and also the command line you used to compile and link it.

Where did you invoke go32-v2, exactly?  Was that in the same place where 
the offending malloc was returning the NULL pointer, or somewhere else?