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.9 required=5.0 tests=BAYES_00,LOTS_OF_MONEY autolearn=ham autolearn_force=no version=3.4.4 X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 103376,a59c0afeb6808e51 X-Google-Attributes: gid103376,public X-Google-ArrivalTime: 2002-09-02 16:26:05 PST Path: archiver1.google.com!news1.google.com!newsfeed.stanford.edu!logbridge.uoregon.edu!news.stealth.net!news.stealth.net!prodigy.com!prodigy.com!newsmst01.news.prodigy.com!prodigy.com!postmaster.news.prodigy.com!newssvr30.news.prodigy.com.POSTED!not-for-mail From: "Pat Rogers" Newsgroups: comp.lang.ada References: <1f358d66.0208302358.6f1c6a39@posting.google.com> <87y9an5tt2.fsf@deneb.enyo.de> <1f358d66.0209020705.6769d948@posting.google.com> <0DMc9.5002$YN.1223639060@newssvr30.news.prodigy.com> Subject: Re: Howto debug seg-faulting Ada 95 code? X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Message-ID: NNTP-Posting-Host: 208.191.182.164 X-Complaints-To: abuse@prodigy.net X-Trace: newssvr30.news.prodigy.com 1031009158 ST000 208.191.182.164 (Mon, 02 Sep 2002 19:25:58 EDT) NNTP-Posting-Date: Mon, 02 Sep 2002 19:25:58 EDT Organization: Prodigy Internet http://www.prodigy.com X-UserInfo1: FKPO@SJGTZYQBQXYQ[OD]_HBWB]^PCPDLXUNNHDK@YUDUWYAKVUOPCW[ML\JXUCKVFDYZKBMSFX^OMSAFNTINTDDMVW[X\THOPXZRVOCJTUTPC\_JSBVX\KAOTBAJBVMZTYAKMNLDI_MFDSSOLXINH__FS^\WQGHGI^C@E[A_CF\AQLDQ\BTMPLDFNVUQ_VM Date: Mon, 02 Sep 2002 23:25:58 GMT Xref: archiver1.google.com comp.lang.ada:28674 Date: 2002-09-02T23:25:58+00:00 List-Id: "Jeffrey Creem" wrote in message news:RNRc9.336566$UU1.57839@sccrnsc03... > > > "Jeffrey Creem" wrote in message > > news:FhMc9.91102$kp.733909@rwcrnsc52.ops.asp.att.net... > > > > > Either use new or declare the variable at the library level (in a > > package) > > > to make it go on the heap. > > > > What has a declaration at the library level have to do with the heap? > > > > > > Techically nothing..I don't believe I have ever read anything in the LRM > that > says for sure that if you declare a variable in a package it goes on the > heap but > if you declare it in a procedure (including the mainline) it goes on the > stack. (See, now > why did Robert have to go and leave...Where is Tucker Taft when you need > him) > > Having said that, every compiler I have used does something like this. It > also tends to > make intuitive sense. Humm, every compiler I have used did not. Declarations within library units are just the first things pushed. We don't think of that initial stack push as being a stack operation because it is never "popped" until the program completes.