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=-0.4 required=5.0 tests=AC_FROM_MANY_DOTS,BAYES_00 autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,c3c4ae45442f569e X-Google-Attributes: gid103376,public X-Google-Language: ENGLISH,ASCII-7-bit Path: g2news1.google.com!news4.google.com!news.glorb.com!news.banetele.no!news.eunet.no!kda-news.kongsberg.com!not-for-mail From: "Egil H. H�vik" Newsgroups: comp.lang.ada Subject: Re: tasks and protected types Date: Fri, 29 Apr 2005 16:06:28 +0200 Organization: News Kongsberg Defence&Aerospace T-Nett Message-ID: References: <1114747457.868019.93210@f14g2000cwb.googlegroups.com> <1114771627.401153.78280@z14g2000cwz.googlegroups.com> <42722ECA.5060903@mailinator.com> NNTP-Posting-Host: kda-mfxp-16.kda.kongsberg.com X-Trace: kda-news.kongsberg.com 1114783317 22396 193.71.174.116 (29 Apr 2005 14:01:57 GMT) X-Complaints-To: tommy.fallsen@kongsberg.com NNTP-Posting-Date: Fri, 29 Apr 2005 14:01:57 +0000 (UTC) X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Xref: g2news1.google.com comp.lang.ada:10820 Date: 2005-04-29T16:06:28+02:00 List-Id: > > > If you will accept a guess: An exception is raised in the first accept > > call. This means that the D1 task terminates (they do that, when you > > have exceptions), but without finishing the accept block. This leaves > > Manage hanging, waiting for D1 (which is dead) to finish its accept > > block. > > I'm too guessing, but I think that when an exception happens inside an > accept, the task gets the exception and the caller gets a Tasking_Error > exception. Kinda like if the exception "splits" and goes to the two > threads. Can someone confirm? RM 9.5.2(26): ... When an exception is propagated from the handled_sequence_of_statements of an accept_statement, the same exception is also raised by the execution of the corresponding entry_call statement. Which means that D1.Start raises an exception, D2.Start is never called, and Manage will wait for D2 to terminate (D1 will terminate due to the unhandled exception) ~egilhh