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=unavailable autolearn_force=no version=3.4.4 Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!feeder.eternal-september.org!nntp-feed.chiark.greenend.org.uk!ewrotcd!newsfeed.xs3.de!io.xs3.de!news.jacob-sparre.dk!franka.jacob-sparre.dk!pnx.dk!.POSTED.rrsoftware.com!not-for-mail From: "Randy Brukardt" Newsgroups: comp.lang.ada Subject: Re: Finalization of library level tasks Date: Wed, 25 Apr 2018 18:46:13 -0500 Organization: JSA Research & Innovation Message-ID: References: Injection-Date: Wed, 25 Apr 2018 23:46:14 -0000 (UTC) Injection-Info: franka.jacob-sparre.dk; posting-host="rrsoftware.com:24.196.82.226"; logging-data="22021"; mail-complaints-to="news@jacob-sparre.dk" X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5931 X-RFC2646: Format=Flowed; Response X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.7246 Xref: reader02.eternal-september.org comp.lang.ada:51712 Date: 2018-04-25T18:46:13-05:00 List-Id: "Dmitry A. Kazakov" wrote in message news:pavqa6$1qdj$1@gioia.aioe.org... ... > Yes. The problem is the order of finalization. For some unclear reason the > task's access type is attempted before the object that contains that > access type because they are in the same scope. It's not unclear - tasks have to terminate before objects are finalized so that the tasks aren't trying to use finalized objects. If the object is a protected object, that could be a really bad deal (remember that finalizing a protected object raises tasking error in any queued task and prevents future calls). We ran into this with Claw, and eventually had the Ada.Task_Identification solution ingrained into the Standard. (I believe you found it from some other messages that I saw previously, so I won't describe it here.) Randy.