Date: Fri, 24 Nov 2000 17:24:57 +0200
From: "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender: halo1 AT zahav DOT net DOT il
To: tractorkillermmg AT aol DOT com (TractorKillerMMG)
Message-Id: <2561-Fri24Nov2000172457+0200-eliz@is.elta.co.il>
X-Mailer: Emacs 20.6 (via feedmail 8.3.emacs20_6 I) and Blat ver 1.8.6
CC: djgpp AT delorie DOT com
In-reply-to: <20001124084843.28804.00001523@ng-cl1.aol.com>
	(tractorkillermmg AT aol DOT com)
Subject: Re: Exiting due to signal SIGSEGV
References:  <20001124084843 DOT 28804 DOT 00001523 AT ng-cl1 DOT aol DOT com>
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
Precedence: bulk

> From: tractorkillermmg AT aol DOT com (TractorKillerMMG)
> Newsgroups: comp.os.msdos.djgpp
> Date: 24 Nov 2000 13:48:43 GMT
> 
> I go to compile Allegro by typing "make" in "C:\DJGPP\allegro" through a dos
> prompt and it screws up.  I get this:
> 
> Compiling Allegro. Please wait...
> gcc -I. -Isrc -Iobj/djgpp -Wall -Wno-unused -m486 -O3 -ffast-math
> -fomit-frame-pointer -o obj/djgpp/stretch.o -c src/stretch.c
> Exiting due to signal SIGSEGV
> Page fault at eip=00154e9a, error=0004
> eax=a8e05d84 ebx=0019278c ecx=ffda76f3 edx=0039f322 esi=00000000 edi=000000c0
> ebp=00322230 esp=00322214 program=C:\DJGPP\LIB\GCC-LIB\DJGPP\2.952\CC1.EXE
> cs: sel=015f  base=835d2000  limit=ffdaefff
> ds: sel=0167  base=835d2000  limit=ffdaefff
> es: sel=0167  base=835d2000  limit=ffdaefff
> fs: sel=013f  base=00012b80  limit=0000ffff
> gs: sel=0177  base=00000000  limit=0010ffff
> ss: sel=0167  base=835d2000  limit=ffdaefff

This is Windows 9X, right?

This is a known, but exceedingly rare problem with GCC on Windows:
when the GCC address space includes addresses near FFFFFFFFh, the
compiler crashes sometimes.

>   Now, with most other times it does this, I can type make about 5 times over
> and it will compile the file.  stretch.c is the only one that does this.  How
> do I fix this, I am a newbie to this.

Try to open one or more DOS boxes on the same system, then type "make"
and see if that helps.

Another thing to try is to type the command line issued by Make (the
one you show above) manually from the DOS prompt.