Hi, On Wed, 2008-03-19 at 14:32 -0500, Carsten Neumann wrote: > Hi again, > > Carsten Neumann wrote: > > I see. I'm still optimistic that an effective but simple solution can be > > found, I'll keep you (and everyone else on the list, of course) posted, > > ok, Gerrit correctly pointed out that locking is only required once the > ThreadManager is up and also how to make sure the lock is initialized by > that time. > This issue should now be fixed in cvs, I'll apply the same fix to 2 > (trunk) as well shortly.
unfortunately I was only half right ;-). I think the init part should be the same as the terminate part, just hard code it into osgInit. The log stuff is basic enough so that should not be a problem. The problem with the initFunction I suggested is that the lock won't be initialised if the Log is not used before the callback is called. Hardcoding it makes sure that no matter what happens after osgInit the lock it there. kind regards, gerrit ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Opensg-core mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/opensg-core
