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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,de85c452b42b049 X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.235.4 with SMTP id ui4mr342788pbc.3.1333571305282; Wed, 04 Apr 2012 13:28:25 -0700 (PDT) Path: r9ni18798pbh.0!nntp.google.com!news1.google.com!news.glorb.com!feeder.erje.net!newsfeed.straub-nv.de!uucp.gnuu.de!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Wed, 04 Apr 2012 22:27:51 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Tasking, AWS and segmentation faults References: <12873826.360.1333555697441.JavaMail.geo-discussion-forums@vbhc14> In-Reply-To: <12873826.360.1333555697441.JavaMail.geo-discussion-forums@vbhc14> Message-ID: <4f7caeb8$0$6640$9b4e6d93@newsspool2.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 04 Apr 2012 22:27:36 CEST NNTP-Posting-Host: e084a966.newsspool2.arcor-online.net X-Trace: DXC=U=JEH7mgo:9;]cDoEWD6A4A9EHlD;3Yc24Fo<]lROoR18kFejV89_@Y5@\]6L9ibFg8`cNT7: X-Complaints-To: usenet-abuse@arcor.de Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: 2012-04-04T22:27:36+02:00 List-Id: On 04.04.12 18:08, tonyg wrote: > > I have a function which is an aws response. In that function I have an array of 86400 records which are processed. I was sort of expecting an error and I got one which is > > Exception name: STORAGE_ERROR > Message: s-intman.adb:139 explicit raise > > I think I need to reserve some space using the storage pragma but I am wondering if anyone experienced in using AWS have any advice If the function "causing" the storage error is in the environment task (main unit), you could allocate more stack space to it. On Unix, the shell's ulimit allows adjusting the amount of stack space available programs. If the function is defined in some Ada task, placing pragma Storage_Size in the task type's declaration will do the trick. If neither solution is satisfactory, you could resort to pointers and manual memory management; see Vadim Godunko's response.