Date: Tue, 18 Feb 1997 12:21:23 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Scott Frazer <frazer AT rtp DOT ericsson DOT se>
cc: djgpp AT delorie DOT com
Subject: Re: emacs 19.34 crashes immediately on win nt 4.0
In-Reply-To: <3308959b.5475968@cnn.exu.ericsson.se>
Message-ID: <Pine.SUN.3.91.970218121808.20000I-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII


On Mon, 17 Feb 1997, Scott Frazer wrote:

> I actually had tried uncommenting the _go32_dpmi_blah_blah line in
> w16selec.c because the one in dosfns.c looked like it would be called
> only once.  I figured that having a little unfreed memory around 
> wouldn't be too bad, but there could be some major accumulation from
> kill/copy's.  It did work for small kill/yank's, but when I killed a
> big chunk of code then tried to yank it back I got dumped to the DOS
> prompt.  No signal explanation, no traceback, nothing ... just c:\

Bad news.  The code on w16select.c only allocates and deallocates DOS 
memory when you kill text longer than 16KB; for smaller kills it uses the 
transfer buffer.  The above means that NT indeed dislikes the way we 
deallocate DOS memory.

I would still like to know whether a small test program that allocates and
deallocates DOS memory crashes on NT (it might be something specific to
Emacs).