X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f
From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10201091606.AA14120@clio.rice.edu>
Subject: Re: Pattern of a program crash
To: djgpp-workers AT delorie DOT com, wojciech DOT galazka AT polkomtel DOT com DOT pl
Date: Wed, 9 Jan 2002 10:06:06 -0600 (CST)
In-Reply-To: <250B3114DA16D511B82C00E0094005F8055AC84E@MSGWAW11> from "=?iso-8859-2?Q?Wojciech_Ga=B3=B1zka?=" at Jan 09, 2002 03:21:50 PM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

> I got a message from someone using NTLFN who says his program no longer
> crashes once NTLFN is loaded.

Another tidbit - this crash only happens if the memory address space is
fragmented and dpmi returns a memory block at a lower address than the
first allocation.  So running multiple programs at once sometimes causes
the problem to happen/disappear.

So loading ntlfn may put memory in the lower memory block to cause it to
be too small for a djgpp 64K sbrk() request - so it goes higher instead
of lower.