It appears that something is wrong in there (or we're missing a lock
somewhere).  Here is what happens in optimized mode:

PeriodicBoundaries point locator object returned NULL!
Stack frames: 5
0: 0   libmesh_oprof.0.dylib               0x0000000102d98390
libMesh::print_trace(std::ostream&) + 64
1: 1   libmesh_oprof.0.dylib               0x0000000102e3b6a4
libMesh::FEGenericBase<double>::compute_periodic_constraints(libMesh::DofConstraints&,
libMesh::DofMap&, libMesh::PeriodicBoundaries const&, libMesh::MeshBase
const&, libMesh::PointLocatorBase const*, unsigned int, libMesh::Elem
const*) + 10308

Again - it only does this about 1 in 10 times.

Also - I have some periodic tests that when run threaded they aren't
failing like this... instead, every once in a while they will give
different answers on the periodic boundaries...

Derek



On Mon, Jul 8, 2013 at 4:54 PM, Roy Stogner <royst...@ices.utexas.edu>wrote:

>
> On Mon, 8 Jul 2013, Derek Gaston wrote:
>
>  It seems like there is something that still isn't thread safe in there.
>>
>> Roy: Maybe you could take a look around there and see if anything
>> rings a bell.  I'm betting that the reason we don't see this with
>> TBB is that our test is so small TBB isn't actually threading it...
>> but with pthreads I split the elements up no matter how many there
>> are... so it is triggering these two tests....
>>
>
> Nothing obviously wrong in there.  The threading danger in PBC code is
> that each thread needs its own sub_point_locator, but the
> ComputeConstraints functor *should* be handling that fine now.
> ---
> Roy
------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel

Reply via email to