From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.3 required=5.0 tests=BAYES_00,INVALID_MSGID autolearn=no autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,ea99a8822847633f X-Google-Attributes: gid103376,public From: "Marc A. Criley" Subject: Re: stack frame too large Date: 2000/11/12 Message-ID: <3A0E9BCC.796E9AD3@earthlink.net>#1/1 X-Deja-AN: 692705510 Content-Transfer-Encoding: 7bit References: <3A0C9FB8.9EBC9A7F@pacbell.net> <3A0D4A91.8C219079@earthlink.net> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii X-Complaints-To: abuse@earthlink.net X-Trace: newsread2.prod.itd.earthlink.net 974039674 158.252.122.130 (Sun, 12 Nov 2000 06:34:34 PST) Organization: Quadrus Corporation MIME-Version: 1.0 NNTP-Posting-Date: Sun, 12 Nov 2000 06:34:34 PST Newsgroups: comp.lang.ada Date: 2000-11-12T00:00:00+00:00 List-Id: Wayne Lydecker wrote: > > > Thanks, that does help. Why is there a limit on the stack frame size? > I played with the above example some more last night and found that > between 1,017 and 1,018 integers (<4Kb) the warning is generated. I > was hoping I could throw a compile, link, or run switch to bump up the > stack frame size. > > Another solution to the problem will be to use pointers. Unfortunately, > there are many instances of this in our code and none of them are nearly > as simple as the above example. After posting my earlier response, I did remember that in a few cases we were able to use pointers. If the data being returned by a function was for reference purposes only, i.e., it wasn't going to be modified, then we "aliased" the data structure and returned a pointer to it via 'Access. Marc A. Criley Senior Staff Engineer Quadrus Corporation