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,e147b0e3a6400ee0,start X-Google-Attributes: gid103376,public From: andrews@njsurfnet.net Subject: task control block and stack size question... Date: 1997/07/07 Message-ID: <868300816.15987@dejanews.com>#1/1 X-Deja-AN: 255310866 X-Http-User-Agent: Mozilla/3.01Gold (WinNT; I) X-Originating-IP-Addr: 128.47.45.72 () Organization: Deja News Usenet Posting Service X-Article-Creation-Date: Mon Jul 07 18:40:17 1997 GMT X-Authenticated-Sender: andrews@njsurfnet.net Newsgroups: comp.lang.ada Date: 1997-07-07T00:00:00+00:00 List-Id: I need some help! We've inherited an Ada project that uses tasking and I have a question on where they could have come up with some numbers they used (none of the original authors are with the company anymore). The main task type uses a representation clause as follows: task type SERVER_TASK_TYPE is entry Initiate ( Socket : CASS_Sockets.Socket_Descriptor ); entry Interrupt; end SERVER_TASK_TYPE; for SERVER_TASK_TYPE'storage_size use 3600 + ( 64 * 1024); -- Task_Control_Block + ( Stack_Size ) Does anybody have any idea about how one comes up with the numbers for the task control block and the stack size? The code is running on a Sun SPARC 20 (Solaris 2.5.1) built by the Sun SPARCWorks Ada 2.1.1 compiler (VADS single threaded RTS). We have a server sending and receiving messages of a perticular size, and when we jack up that size, the server seems to hang. After jacking the 64 * 1024 to 256 * 1024, it seems to work for a few API calls, but then hangs. I need more info about where these numbers came from! Any ideas? Thanks ALL! Pete Andrews -------------------==== Posted via Deja News ====----------------------- http://www.dejanews.com/ Search, Read, Post to Usenet