Re: Patch to DorothyLocker

Thomas Klaeger <[email protected]> Wed, 22 Sep 2004 11:55:25 +0200
Newsgroups gmane.comp.pythin.pyds.devel
Message-ID <[email protected]>
Is there any possibility I can help out?

Garth T Kidd schrieb:
> Aah, bugger. I've replaced one deadlock with another; it's just happening on
> Events because every other tool talks to it. I'll have to re-do large
> chunks. 
> 
> -----Original Message-----
> From: Garth T Kidd [mailto:garth-OnzZ1s1DREKDegMON/[email protected]] 
> Sent: Wednesday, 22 September 2004 2:31 PM
> To: 'Garth T Kidd'; 'Thomas Klaeger'; 'pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]'
> Subject: RE: [Pyds-dev] Patch to DorothyLocker
> 
> Okay; my first and most major blunder was that DorothyRLock wasn't
> thread-safe. What's left, after fixing that and a couple more bugs, is that
> the code to print details about foreign owners just isn't right. I'll fix
> it. What'll be left after *that* is a blockade on the Events tool. 
> 
> -----Original Message-----
> From: pyds-dev-admin-iYtK5bfT9M//Ad8WF/[email protected]
> [mailto:pyds-dev-admin-iYtK5bfT9M//Ad8WF/[email protected]] On Behalf Of Garth T Kidd
> Sent: Wednesday, 22 September 2004 11:18 AM
> To: 'Thomas Klaeger'; pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]
> Subject: RE: [Pyds-dev] Patch to DorothyLocker
> 
> I'll have to re-test. I can't incorporate the patches as-is because they're
> broken: Rlocks can be locked multiple times by the same thread, and your
> added lockContext attributes bypass my stack of lock details. 
> 
> -----Original Message-----
> From: pyds-dev-admin-iYtK5bfT9M//Ad8WF/[email protected]
> [mailto:pyds-dev-admin-iYtK5bfT9M//Ad8WF/[email protected]] On Behalf Of Thomas Klaeger
> Sent: Monday, 20 September 2004 8:41 PM
> To: pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]
> Subject: [Pyds-dev] Patch to DorothyLocker
> 
> DorothyLocker raised exceptions if a lock was held by another task. In this
> case the lockContext and lockTime was not defined although it should have
> been.
> 
> Additionally it whined about unable to lock long after the lock had been
> acquired due to the LockWhiner not checking if it has been stopped before
> whining.
> 
> 
> _______________________________________________
> Pyds-dev mailing list
> Pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]
> http://www.westfalen.de/cgi-bin/mailman/listinfo/pyds-dev
> 
> 
> _______________________________________________
> Pyds-dev mailing list
> Pyds-dev-iYtK5bfT9M//Ad8WF/[email protected]
> http://www.westfalen.de/cgi-bin/mailman/listinfo/pyds-dev
>