|
From: | Richard Frith-Macdonald |
Subject: | [bug #35263] libobjc2 can enter a deadlock during dtable initialization |
Date: | Thu, 19 Jan 2012 13:58:51 +0000 |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_6_8) AppleWebKit/534.52.7 (KHTML, like Gecko) Version/5.1.2 Safari/534.52.7 |
Follow-up Comment #8, bug #35263 (project gnustep): > If you only got the global lock, you have to make sure that every single class that might potentially receive messages in another thread is initialized before you go multi-threaded, On the contrary ... with the gnu runtime all you have to do is avoid any +initialize waiting for another thread ... which is a *very* easy contract to honor. But the discussion of which contract is *easier* is rather academic ... in practice we have to try to honor both contracts :-( _______________________________________________________ Reply to this item at: <http://savannah.gnu.org/bugs/?35263> _______________________________________________ Message sent via/by Savannah http://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |