Nope - it's not that the PointLocator is NULL... the PointLocator is
_returning_ NULL (ie it couldn't find an element).
Look at line 1956 in fe_base.C
Derek
On Mon, Jul 8, 2013 at 9:28 PM, Roy Stogner <royst...@ices.utexas.edu>wrote:
>
> On Mon, 8 Jul 2013, Derek Gaston wrote:
>
> 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
>>
>
> Wait - so NULL is getting passed in as that PointLocatorBase*? That
> should *never* happen.
>
> If you could trace that back any further (does the sub_point_locator()
> call in ComputeConstraints fail? the sub_point_locator_call() in
> create_dof_constraints?) then we're getting much closer to the root of
> the problem.
> ---
> 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
