Date: Mon, 07 Jun 1999 13:22:59 -0500
From: Eric Rudd <rudd AT cyberoptics DOT com>
Subject: Re: cwsdpmi r5
To: djgpp-workers AT delorie DOT com
Message-id: <375C0E03.28F2B72F@cyberoptics.com>
Organization: CyberOptics
MIME-version: 1.0
X-Mailer: Mozilla 4.05 [en] (Win95; U)
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <9906011841 DOT AA15376 AT clio DOT rice DOT edu>
Reply-To: djgpp-workers AT delorie DOT com

Charles Sandmann wrote:

> I've decided it's time to do a cwsdpmi r5, so I'm listening to requests.

The biggest problem I've had is a propensity for gcc to crash on systems which use HIMEM.SYS
but not EMM386 or Windows.  The symptoms, which occur on about 1% of the compilations, are a
bomb in an RMCB with a traceback.  The keyboard then invariably locks up, necessitating a hard
re-boot, though the disk cache continues to commit normally after the lock-up.  I have
observed this problem on several computers.  Oddly enough, my own DJGPP-compiled apps have
never had this problem.

I don't know for a fact that CWSDPMI is involved in this, but since EMM386 (or Windows) seems
to prevent these lock-ups makes me suspect that CWSDPMI is involved.

Since I have no reason to use EMM386 (other than to prevent this problem), and since EMM386
interferes with other things on my system, it would be nice not to have to use EMM386.

I don't know what I can do to diagnose the problem, other than to manually transcribe the
traceback.

This is an old problem I've lived with for a couple of years, which I have reported before,
but it hasn't gone away.

-Eric Rudd
rudd AT cyberoptics DOT com