Date: Tue, 8 Jun 1999 09:30:30 +0200
From: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
To: djgpp-workers AT delorie DOT com
Subject: Re: cwsdpmi r5
Message-ID: <19990608093030.B14310@duna91.eth.ericsson.se>
References: <9906011841 DOT AA15376 AT clio DOT rice DOT edu> <375C0E03 DOT 28F2B72F AT cyberoptics DOT com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Mailer: Mutt 0.95.6i
In-Reply-To: <375C0E03.28F2B72F@cyberoptics.com>; from Eric Rudd on Mon, Jun 07, 1999 at 01:22:59PM -0500
Reply-To: djgpp-workers AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Mon, Jun 07, 1999 at 01:22:59PM -0500, Eric Rudd 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.

This problem happened to me several times over the years using a
similar setup (ie. himem.sys only). Sometimes when I type `make', and
when make finishes I see this traceback and my machine hangs. It's very
rare and totally nondeterministic unfortunately. A fix would be nice
though ;-)

Laszlo