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, MSGID_RANDY 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: Robert Dewar Subject: Re: storage size pragmas Date: 2000/05/07 Message-ID: <8f4r8a$c80$1@nnrp1.deja.com>#1/1 X-Deja-AN: 620428242 References: <20000507094954.10742.00001811@ng-bj1.aol.com> <3915BC28.A0D56A68@telepath.com> X-Http-Proxy: 1.0 x34.deja.com:80 (Squid/1.1.22) for client 205.232.38.14 Organization: Deja.com - Before you buy. X-Article-Creation-Date: Sun May 07 22:38:03 2000 GMT X-MyDeja-Info: XMYDJUIDrobert_dewar Newsgroups: comp.lang.ada X-Http-User-Agent: Mozilla/4.61 [en] (OS/2; I) Date: 2000-05-07T00:00:00+00:00 List-Id: In article <3915BC28.A0D56A68@telepath.com>, Ted Dennison wrote: > 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. Also be careful that even if a storage error fault is signalled in a task, the usual effect is to make the task terminate silently, which can have pretty horrible effects on your program. Sent via Deja.com http://www.deja.com/ Before you buy.