On Aug 17, 2013, at 12:35 AM, Derek Gaston <[email protected]> wrote:
> Pthread locks work by being 0 in their unlocked state and anything > else when they are locked. I can only guess that the constructor for > those mutexes hasn't yet been called to set the initial value of the > lock... therefore it's waiting there. > > I won't have access to either of those machines to do more testing > until next week. Agreed that sounds like the issue. Could you check that in down the line when you get access? > For now, I vote for removing those locks as they are unnecessary. Agreed on this point too. Please confirm though this is only the Singleton::Setup::Setup() mutex, and not also the one a few lines below in void Singleton::setup ()? -Ben ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
