www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/09/23/10:47:30

Date: Tue, 23 Sep 1997 17:46:48 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Andrew Ellem <krand AT ican DOT net>
cc: DJGPP Mailing List <djgpp AT delorie DOT com>
Subject: Re: Allegro WIP (make.exe crash)
In-Reply-To: <3427C4E0.B8A42C38@ican.net>
Message-ID: <Pine.SUN.3.91.970923174036.15819B-100000@is>
MIME-Version: 1.0

On Tue, 23 Sep 1997, Andrew Ellem wrote:

> In the Win95 Dos box go32-v2 gave me this:
> 
> DPMI memory available 		10671 kb
> DPMI swap space available 	2681 kb
> 
> I have set my dos box's properties to "65535" DPMI and have 16megs
> of ram and 100+ megs free on my HD.

Is the above report by go32-v2 before or after you set DPMI to 65535K?  
If it's after, then I don't understand how can that be.  You tell Windows 
to let you use 64MB of DPMI memory, so the sum of the two numbers 
reported by go32-v2 should be 64MB.  This is what I see on my machine.

After you set DPMI memory to 64MB, did it compile from Windows DOS box, or 
does it still crash?

> Here's the traceback of my attempt in "restart to MS-DOS":
> 
> Compiling the djgpp version of Allegro. Please wait...
> gcc -I. -Isrc -Isrc/djgpp -Iobj/djgpp -Wall -W -Werror -m486 -O3
> -ffast-math -fomit-frame-pointer -o obj/djgpp/colblend.o -c src/colblend.c
> Exiting due to signal SIGSEGV
> Page fault at eip=000ef69e, error=0006

Did you try to bump up CWSDPMI's internal tables size, as the FAQ 
suggests in section 6.4?  If not, please do so and see if that helps.

Another thing to try is to stubedit cc1.exe and enlarge its stack size 
(see section 6.3 in the FAQ).

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019