cvs.gedasymbols.org/archives/browse.cgi | search |
From: | NonReal <nonreal AT geocities DOT com> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: "big" arrays and the stack |
Date: | Mon, 29 Dec 1997 08:34:23 -0700 |
Organization: | Colorado State University, Fort Collins, CO 80523 |
Lines: | 12 |
Message-ID: | <34A7C2FF.390A@geocities.com> |
References: | <01bd13ea$293d4c40$a8dcc7c7 AT suzie> <34A73B4B DOT A430C820 AT cornell DOT edu> |
Reply-To: | nonreal AT geocities DOT com |
NNTP-Posting-Host: | ts1312.slip.colostate.edu |
Mime-Version: | 1.0 |
To: | djgpp AT delorie DOT com |
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> i have no idea what you mean here, but the difference is whether the > array is global or allocated on the stack. the default stack size for > djgpp programs is 256Kb, so a local array larger than that will corrupt > the stack, leading to a crash. you can either increase the size of the > stack, or, better IMO, allocate such a large amount of memory > dynamically. How do you change the stack size? I've got a nasty recursive program that would love more space to work in :) *wave* -Tim
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |