www.delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1998/10/21/03:12:25

Date: Wed, 21 Oct 1998 09:10:11 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: russell DOT thamm AT dsto DOT defence DOT gov DOT au
cc: djgpp AT delorie DOT com
Subject: Re: DJGPP & 256 MB
In-Reply-To: <70jr47$k0s$1@nnrp1.dejanews.com>
Message-ID: <Pine.SUN.3.91.981021090108.22991J-100000@is>
MIME-Version: 1.0
Reply-To: djgpp AT delorie DOT com

On Wed, 21 Oct 1998 russell DOT thamm AT dsto DOT defence DOT gov DOT au wrote:

> My program has a 118 MByte data structure and it causes a segmentation
> fault while loading. If I halve the size of this data structure, the
> program runs OK.

It might be that you allocate the memory in too large chunks.  Chapter 15 
describes and explains such gotchas.

Invoke go32-v2 with no arguments and see what it reports.  If it reports 
a number sufficiently close to 256MB, then your DJGPP setup is okay and 
the problem is in the specific ways your program tries to allocate 
memory.  In that case, tell more about how do you allocate RAM, or throw 
together a short test program which exhibits the same problem and post 
its source.

If go32-v2 reports 128MB, post your configuration files (CONFIG.SYS and 
AUTOEXEC.BAT).

> Even if I could get it to work without EMM386 (which I can't),

Why can't you toss EMM386?

> I have so
> little base memory left that I keep getting "out of memory errors" during
> compilation.

Is it GCC that complains about out of memory?  If so, it cannot be 
because of the conventional memory, since GCC only uses about 70KB of it;
the rest is in extended memory, above 1MB mark.  There's something 
strange going on here; please post the complete compilation trace printed 
when you add -v to the compilation command line.  (Use `redir' to 
redirect stderr to a file.)

- Raw text -


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