From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10206121508.AA22074@clio.rice.edu>
Subject: Re: unixy sbrk and win2k
To: djgpp-workers AT delorie DOT com
Date: Wed, 12 Jun 2002 10:08:09 -0500 (CDT)
In-Reply-To: <3D066A51.93411C96@phekda.freeserve.co.uk> from "Richard Dawe" at Jun 11, 2002 10:23:29 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 launch bash (using a shortcut) from Emacs, hold down Ctrl and the whole
> window vanishes - no more Emacs or bash. I don't see any traceback. From
> memory: Even if I turn on the 'Don't Close Window On Exit', I don't see a
> traceback. IIRC the window still vanishes.

This is common when NTVDM goes away.  

> Emacs does work, if I don't hold down Ctrl, but crashes after some time, when
> you press Ctrl. It seems to be fairly random when it crashes. Since Ctrl is
> fairly crucial to using Emacs, it's only a matter of time!
> 
> I haven't tried running Emacs directly using a shortcut. I'll try that next
> time I have access to VMware (I'm not running Linux right now on my
> development PC).

Do this (important test).  Launch cmd.exe.  If you launch the task manager,
sort by image name, check the number of NTVDM.EXE images.  Run emacs,
you should see a new NTVDM.  Record it's PID.  Do the CTRL thing, does it's
PID go away when it exits?  The cmd window will remain.  Do you get any
other info, or just dropped back to command line (when NTVDM aborts you
typically just go back to the prompt with no message).

This test determines if it happens without nesting (important fact), if 
there is any crash info (important fact), if NTVDM dies (important).
Does it go away if you are not using unixy sbrk?

If it happens standalone, and NTVDM dies, then it indicates something 
in the hardware interrupt routine isn't quite right.