RE: RE: Timing events in GNAT GPL 2006

["Vo, Anh \(US SSA\)" <anh.vo@baesystems.com>]

-----Original Message-----
From: comp.lang.ada-bounces@ada-france.org
[mailto:comp.lang.ada-bounces@ada-france.org] On Behalf Of Vo, Anh (US
SSA)
Sent: Monday, January 15, 2007 8:30 AM
To: Rolf Ebert; comp.lang.ada@ada-france.org
Subject: RE: RE: Timing events in GNAT GPL 2006

-----Original Message-----
From: Rolf Ebert [mailto:rolf.ebert_nospam_@gmx.net] 
Sent: Sunday, January 14, 2007 5:10 AM
To: Vo, Anh (US SSA); comp.lang.ada@ada-france.org
Subject: Re: RE: Timing events in GNAT GPL 2006


<< > There are three things wrong with your codes. Two of them are
critical.
> 1. The protected procedure Inc_Clock has wrong parameter mode. It must
> be in out mode.
> 2. The call Set_Handler from the protected procedure will result in a
> deadlock it is run.
> 3. Protected object must be declared at the library level. Yours is
not.
> As the result, non-local pointer cannot point to local object error at
> lines 20 and 26

<<<$$$ OK, I fixed issues 1 and 3 in my code and I can observe issue 2.
I don't
understand, however, why the deadlock occurs. Is the deadlock required
by the RM or is it just due to GNAT's implementation of Timing_Events?
>>

This deadlock occurred when I tested it. I was supposed to find out why?
But, I have not had a chance to investigate it yet. $$$>>>

OK, I have some good news to share. The deadlock has been fixed in
GNAT/GCC- 4.3-20070119 on RedHat. Therefore, the handoff task is no
longer needed.

AV