Xref: news2.mv.net comp.os.msdos.djgpp:3166 From: Broeker AT axp03 DOT physik DOT rwth-aachen DOT de (Hans-Bernhard Broeker) Newsgroups: comp.os.msdos.djgpp Subject: Re: problem with DJGPP and arrays. Date: 25 Apr 96 11:53:32 GMT Organization: RWTH -Aachen / Rechnerbetrieb Informatik Lines: 41 Message-ID: References: <4lk5mk$rl4 AT news DOT nevada DOT edu> NNTP-Posting-Host: axp03.physik.rwth-aachen.de To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp gaghon AT nevada DOT edu (GEORGE GAGHON) writes: I think we need some additional information to really diagnose that problem: >Ok I am having a problem with DJGPP and large arrays. All my arrays do >not exceed 2megs of RAM (combined). >I have the arrays inited like so: >int array1[20000], array2[10000], array3[70000] ... >... >int array7[5300], array8[1200] ... >... >int array 12[70000] But, *where* are they inited? I.e. are those definitions inside a function or outside? If they are inside, I'd suspect you are hitting the limited stacksize of DJGPP programs (256Kb by default, can be stubedit'ed). Had you posted a complete example source, demonstrating the erroneous behaviour, this information would have been present in there :-( >When I try to binary load using _open or fopen, when I get to array7[] >I get an traceback error like so... Here, again, you left out the more important parts of the error message: the actual message and the register dump. >If I put a dummy array in like: >int array_dummy[5300], array7[5300], array8[1200]... >then it works ok. Strange... Please, read the FAQ, guys! There's a reason for the instructions it contains about preparing a problem report, really! Hans-Bernhard Broeker (Aachen, Germany)