Message-ID: <MAPI.Id.0016.00333138303633303030303930303058@MAPI.to.RFC822>
X-MSMail-Priority: Normal
X-Priority: 3
To: djgpp-workers AT delorie DOT com
Cc: nate AT cartsys DOT com, sandmann AT clio DOT rice DOT edu, pavenis AT lanet DOT lv
MIME-Version: 1.0
From: "Erik Berglund" <erik2 DOT berglund AT telia DOT com>
Subject: Re: gcc-crash - and a possible solution
Date: Tue, 06 Jul 99 01:43:10 +0100 (DJG)
Content-Type: text/plain; charset="ISO-8859-1"; X-MAPIextension=".TXT"
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

On Mon, Jun 28, 1999, Nate Eldredge wrote:

> If you're rebuilding GCC anyway, you might consider throwing my YAMD at
> it and see if it reports anything going amiss.
>
> http://www.cartsys.com/eldredge/n/yamd/
> 
> Just a thought...

Hi,

Thanks a lot, I think I will download and test it soon.
To solve my current interesting problem with gcc, it could be
useful to look at what win3.11 DPMI does with the physical
memory mapping, perhaps. I don't know if YAMD supports
that, but it certainly looks useful for other error cases anyway.

--
Erik