Date:	Sun, 17 Dec 2000 12:21:57 +0200 (WET)
From:	Andris Pavenis <pavenis AT lanet DOT lv>
To:	djgpp AT delorie DOT com
Subject:	Re: gcc.exe barfs on simple hello.c file.
In-Reply-To:	<Pine.SUN.3.91.1001217093212.3325O-100000@is>
Message-ID:	<Pine.A41.4.05.10012171212420.100456-100000@ieva06.lanet.lv>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Sun, 17 Dec 2000, Eli Zaretskii wrote:

> 
> On Sat, 16 Dec 2000, secross wrote:
> 
> > Hello, I just downloaded the latest djgpp compiler and the gcc.exe does
> > a sigsegv on a simple hello.c (hello world) file.
> 
> Is this 100% reproducible?  That is, does it crash each time you compile 
> hello.c, or only sometimes?
> 
> > I have a 486-dx66 machine with 32Megs of ram.
> 
> I suspect some hardware problem.  Could you please try to play with the 
> CMOS settings related to memory, caches, etc.?  (The FAQ has some advice 
> about this in section 6.6.)

I once saw bad behaviour of one 486 box when tried to run DJGPP compiled
programs (not a compiler itself though). Real mode DOS applications worked
mostly Ok. When I tried to build DJGPP app with memory allocation
debugger included (I used Fortify-2.2) I saw random changes of single bits
in deallocated memory: I think rather evidently pointing to hardware
problems.

It appeared that poeple who sold used machine have put EDO memory in
matherboard which doesn't support it. It appeared that one more nearby
486 box had non EDO memory but motherboard supported it ...

In this case these crashes were at random places of course 


> 
> > allegro does not seem to compile either when running make , with the same gpf.
> 
> Is the GPF *exactly* the same?  If even one bit there differs, please 
> post the crash message from _both_ crashes.  The information there is 
> very important.
> 

- Raw text -