Guys,
We're seeing hard locks on some machines in Singleton::Setup::Setup()!
The problem is that it's trying to create a scoped_lock using a mutex that
is defined in that file.
Apparently that mutex is not guaranteed to have been initialized at the
point where we're calling that function (or som
On Fri, 16 Aug 2013, Derek Gaston wrote:
We're seeing hard locks on some machines in Singleton::Setup::Setup()!
The problem is that it's trying to create a scoped_lock using a mutex that is
defined in that file.
Apparently that mutex is not guaranteed to have been initialized at the point
w
A couple of things:
1. This only happens with pthreads (ie it doesn't happen with TBB).
2. I can confirm that it is the same symptom on the Intel Phi card.
3. I can confirm that it is alleviated by commenting out those
scoped_lock lines (for both machines).
Pthread locks work by being 0 in t
