Re: Dynamic allocation of tasks

[Florian Weimer <fw@deneb.cygnus.argh.org>]

Robert Dewar <robert_dewar@my-deja.com> writes:

> > I found no way to complete a task before its allocator
> completes.
> 
> terminate task (e.g. abort it), then use unchecked
> deallocation (see RM D.12(4)).

I tried this (with GNAT 3.12p), and it didn't work (there was a resource
leak, of both memory and kernel threads IIRC).  After reading the RM,
I was convinced that I couldn't expect an implementation to support
this, but a more careful study revealed that it's probably reasonable
to expect this behavior (abort of task causes abnormal completion of
the task body, but it *does* cause completion, which means the task
body is finalized next, and, after that, it is terminated).

What's the effect of an abort statement if the task in question is
blocked in a syscall (such as read(2))?