Also, it didn't happen in earlier versions of LibMesh, for example 0.9.2. Thanks, Harshad
On Wed, Aug 2, 2017 at 3:35 AM, Harshad Sahasrabudhe <hsaha...@purdue.edu> wrote: > Hi Roy, > > I'm using version 1.1. The crash only happens with 2 or more processes. It > doesn't happen on a single process. > > Thanks, > Harshad > > On Tue, Aug 1, 2017 at 3:26 PM, Roy Stogner <royst...@ices.utexas.edu> > wrote: > >> >> On Tue, 1 Aug 2017, Harshad Sahasrabudhe wrote: >> >> I got a segfault when I called the PointLocatorTree::operator() function. >>> Does anyone know why the segfault? Thanks! Here's the backtrace: >>> >> >> What libMesh version are you using? Those line numbers don't seem to >> match up to master or 1.2.x. >> >> If I'm right about the line number offset between whatever you're >> using and master, though, it looks like the segfault is either a NULL >> element dereference or a dangling pointer dereference in find_element. >> I don't know what could cause the former to happen. The latter could >> happen if you deleted mesh elements without rebuilding the point >> locator afterwards, maybe? >> --- >> Roy >> >> >> (gdb) bt >>> #0 0x00002aaffd5a5e7b in libMesh::TreeNode<8u>::find_element >>> (this=0x5a6f810, >>> p=..., allowed_subdomains=0xd6, relative_tol=9.9999999999999995e-07) >>> at src/utils/tree_node.C:481 >>> #1 0x00002aaffd5a5a72 in libMesh::TreeNode<8u>::find_element_in_children >>> ( >>> this=0x5a6f810, p=..., allowed_subdomains=0xd6, >>> relative_tol=9.9999999999999995e-07) at src/utils/tree_node.C:513 >>> >> > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
