I'm trying to use the Mesh::point_locator() in threads... and I'm hitting a
segfault:
* thread #2: tid = 0xec2ba, 0x0000000100e8b400
libmesh_opt.0.dylib`libMesh::TreeNode<4u>::~TreeNode() + 48, stop reason =
EXC_BAD_ACCESS (code=1, address=0x9)
* frame #0: 0x0000000100e8b400
libmesh_opt.0.dylib`libMesh::TreeNode<4u>::~TreeNode() + 48
frame #1: 0x0000000100e8b411
libmesh_opt.0.dylib`libMesh::TreeNode<4u>::~TreeNode() + 65
frame #2: 0x0000000100e88424
libmesh_opt.0.dylib`libMesh::Tree<4u>::~Tree() + 36
frame #3: 0x0000000100e625d3
libmesh_opt.0.dylib`libMesh::PointLocatorTree::~PointLocatorTree() + 51
frame #4: 0x0000000100bf72da
libmesh_opt.0.dylib`libMesh::MeshBase::point_locator() const + 74
I wonder if this could be behind the errors I saw with Periodic BCs with
threading recently...
Is the Mesh::point_locator() supposed to be usable with threads? If not,
what's the recommended way to use a PointLocator with threads?
Derek
------------------------------------------------------------------------------
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
