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 autolearn=ham
	autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,c6e969ef19591b55,start
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2001-09-18 05:48:24 PST
Path: 
 archiver1.google.com!newsfeed.google.com!newsfeed.stanford.edu!newsfeeds.belnet.be!news.belnet.be!npeer.kpnqwest.net!newsfeed.ath.cena.fr!ath.cena.fr!not-for-mail
From: Nicolas HUYNH <HUYNH_Nicolas@ath.cena.fr>
Newsgroups: comp.lang.ada
Subject: TASKING_ERROR or STORAGE_ERROR ?
Date: Tue, 18 Sep 2001 14:47:12 +0200
Organization: C.E.N.A. (Centre d'Etudes de la Navigation
 =?iso-8859-1?Q?A=E9rienne?=)
Message-ID: <3BA74250.C1AB7F6C@ath.cena.fr>
NNTP-Posting-Host: gollum.dev.ath.cena.fr
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Trace: albert.ath.cena.fr 1000817063 27612 172.16.76.35 (18 Sep 2001
 12:44:23 GMT)
X-Complaints-To: usenet@ath.cena.fr
NNTP-Posting-Date: 18 Sep 2001 12:44:23 GMT
X-Mailer: Mozilla 4.7 [en] (X11; I; SunOS 5.7 sun4u)
X-Accept-Language: en, fr
Xref: archiver1.google.com comp.lang.ada:13148
Date: 2001-09-18T12:44:23+00:00
List-Id: <comp.lang.ada>

Hi,

I've got problems with Ada tasks at elaboration time, using
Gnat and Linux.
The pattern is the following for several packages P :

package P is
   (...)
   task type TT is (...)
   T : TT;
   (...)
end P;

package body P is
   (...)
   task body TT is
   begin
      (...)
   end TT;
   (...)
end P;

On Solaris and Tru64-Unix, I used to set the Storage_Size attribute
of each task. No problem.

However, on Linux, my program raises an exception TASKING_ERROR
when elaborating the package P. In many cases, I solved the problem
by decreasing the Storage_Size of the task, thus it appears that this
was a problem due to storage during the elaboration of the task itself.

But there is one case when this does not work.
Changing the body of the task by a much more simple one also suppresses
the TASKING_ERROR, but of course I would like to keep the body of
the task unchanged.

Is there any way to investigate any more ?

Any help would be appreciated !

Nicolas