www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/09/17/04:31:29

Date: Thu, 17 Sep 1998 11:31:25 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: jtgalkowski AT alum DOT mit DOT edu
cc: djgpp AT delorie DOT com
Subject: Re: Recently installed version of DJGPP's gcc hangs
In-Reply-To: <6tovn5$h7k$1@nnrp1.dejanews.com>
Message-ID: <Pine.SUN.3.91.980917113103.10789F-100000@is>
MIME-Version: 1.0

On Wed, 16 Sep 1998 jtgalkowski AT alum DOT mit DOT edu wrote:

> Ran for over an hour on 25 MHz (I know, slow) 486.  Result was
> the Page Fault in RMDB reported earlier today.

After looking into the source you sent me, I'm now positive that my
previous guess was correct.  The file toam.c is in a nutshell a huge
`switch' statement with a lot of cases.  Such sources are known to
require preposterous amounts of memory while GCC compiles them, and
also a lot of stack space.

So, in addition to bumping up the CWSDPMI heap size, as I suggested
before, you should also increase the stack size available to cc1.exe,
the C compiler invoked by GCC:

    stubedit c:/djgpp/lib/gcc-lib/djgpp/2.81/cc1.exe minstack=1024k

Be sure to change the pathname of cc1.exe if it is installed in a
different directory on your machine.  Also, if 1MB of stack is not
enough (i.e., if the compiler still crashes), enlarge it even more.

Btw, the DJGPP FAQ (v2/faq211b.zip from the same place you get DJGPP)
describes this kind of failures and describes how to solve them in
section 6.6.

- Raw text -


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