Re: Stack, task size and DEC Ada

[Mats Weber <Mats.Weber@elca-matrix.ch>]

> There is, in the predefined units, a GET_TASK_INFO unit that permits a
> direct access to internal task information. It's thus possible to
> dynamically get the task type name, task id, ... and, most of all, a few
> parameters that seem to be interesting : the task stack top and base.
> 
> I thought to myself with these functions I'll be able to write a small
> routine that declares a (small) variable, I'll take the adress of this
> variable and compare it to either the top or the base of the stack and
> I'll know (nearly) how much of the stack of my task is currently used.
> It was great I could with this little probe evaluate (roughly) the stack
> used in particular places in my program.

You probably don't need this in your code once it is in production.
While you are developping, you can use the VMS Ada debugger to look at
how much stack space each task has consumed and then do the necessary
adjustments. The useful commands are:

<<first set a breakpoint at a point before all the tasks go away>>
dbg> sho task/all                  -- shows the list of all tasks
dbg> sho task/full %task<number>   -- shows info (including stack) about
a task

--Mats