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,11d70610d4cc79b7 X-Google-Attributes: gid103376,public From: Ted Dennison Subject: Re: storage size pragmas Date: 2000/05/07 Message-ID: <3915BC28.A0D56A68@telepath.com>#1/1 X-Deja-AN: 620361874 Content-Transfer-Encoding: 7bit References: <20000507094954.10742.00001811@ng-bj1.aol.com> X-Accept-Language: en,pdf Content-Type: text/plain; charset=us-ascii X-Complaints-To: Abuse Role , We Care X-Trace: monger.newsread.com 957725390 216.14.8.10 (Sun, 07 May 2000 14:49:50 EDT) Organization: Telepath Systems (telepath.com) MIME-Version: 1.0 NNTP-Posting-Date: Sun, 07 May 2000 14:49:50 EDT Newsgroups: comp.lang.ada Date: 2000-05-07T00:00:00+00:00 List-Id: ANTHONY GAIR wrote: > For those of you watching my progress with Ada tasks and segmentation faults > with both bated breath and intrepidation for the next exciting installment. > > Would a large array stored inside a task cause a segmentation fault if no > storage size pragma is used ? Well, my first guess when I see the words "exception" and "task" together is typically that the user made some big honking object in his task that blew out the default stack size for tasks. However, since that usually causes Storage_Error rather than a seg fault, I figured that probably wasn't it, and didn't say anything about it. Try jacking up the task's stack to ridiculous levels with "for Taskname'Storage_Size use" or a "pragma Storage_Size". If that fixes it, send a bug report to your vendor. I believe the condition of running out of stack space should cause Storage_Error, not a seg fault. -- T.E.D. Home - mailto:dennison@telepath.com Work - mailto:dennison@ssd.fsi.com WWW - http://www.telepath.com/dennison/Ted/TED.html ICQ - 10545591