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 09:48:03 PST
Path: 
 archiver1.google.com!news1.google.com!newsfeed.stanford.edu!canoe.uoregon.edu!logbridge.uoregon.edu!newsswitch.lcs.mit.edu!nntp.flash.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" <progers@classwide.com>
Newsgroups: comp.lang.ada
References: <1f358d66.0208302358.6f1c6a39@posting.google.com>
 <87y9an5tt2.fsf@deneb.enyo.de>
 <1f358d66.0209020705.6769d948@posting.google.com>
 <FhMc9.91102$kp.733909@rwcrnsc52.ops.asp.att.net>
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: <0DMc9.5002$YN.1223639060@newssvr30.news.prodigy.com>
NNTP-Posting-Host: 208.191.182.164
X-Complaints-To: abuse@prodigy.net
X-Trace: newssvr30.news.prodigy.com 1030985276 ST000 208.191.182.164 (Mon,
 02 Sep 2002 12:47:56 EDT)
NNTP-Posting-Date: Mon, 02 Sep 2002 12:47:56 EDT
Organization: Prodigy Internet http://www.prodigy.com
X-UserInfo1: 
 FKPO@MC@@S@USVT^ORHL_IXBUSXHQD\MNPWZKB]MPXHNDQUBLNTC@AWZWDXZXQ[K\FFSKCVM@F_N_DOBWVWG__LG@VVOIPLIGX\\BU_B@\P\PFX\B[APHTWAHDCKJF^NHD[YJAZMCY_CWG[SX\Y]^KC\HSZRWSWKGAY_PC[BQ[BXAS\F\\@DMTLFZFUE@\VL
Date: Mon, 02 Sep 2002 16:47:56 GMT
Xref: archiver1.google.com comp.lang.ada:28661
Date: 2002-09-02T16:47:56+00:00
List-Id: <comp.lang.ada>

"Jeffrey Creem" <jeff@thecreems.com> wrote in message
news:FhMc9.91102$kp.733909@rwcrnsc52.ops.asp.att.net...
<snip>
> You are blowing the stack because you are trying to declare a large
> structure on within a procedure (be it the main procedure or a sub
> program)..
>
> 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?