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,a769f1543f681862
X-Google-Attributes: gid103376,public
From: dewar@merv.cs.nyu.edu (Robert Dewar)
Subject: Re: Question: VADSself Ada Tasking on DEC Alpha Digital UNIX
 Multiprocessor
Date: 1997/04/27
Message-ID: <dewar.862140993@merv>#1/1
X-Deja-AN: 237699776
References: <01bc4f41$f609fed0$0b598986@greg2>
Organization: New York University
Newsgroups: comp.lang.ada
Date: 1997-04-27T00:00:00+00:00
List-Id: <comp.lang.ada>


Sean Lane Fuller says

<<Help.  It seems to me that on the DEC Alpha
platform, Ada tasking does not free up
allocated task memory after the task has
exited.  Is this right?  Is there a work around?
I have attached a small sample code that should be able
to run forever, but instead steadily allocates memory.
I can leave out the unchecked_deallocation
in the sample code and I get the same problem.>>

That is to be expected on most Ada 83 implementations given the Rosen
anomoly, for which there used to be an ACVC test (this is the test
that makes sure that you can test 'Terminated of dead tasks .. the
easiest solution to this is just to keep all tasks around till the
type is out of scope.