>
> Oh, I think I forgot to ask before: you have run this in dbg mode,
> right? And it still segfaults there, it doesn't throw an error? I
> saw a stack trace with line numbers so I figured "he's not in opt",
> but I suppose you could have been in devel, and devel honestly isn't
> good enough for
On Wed, 2 Aug 2017, Harshad Sahasrabudhe wrote:
ReplicatedMesh or DistributedMesh?
I'm using DistributedMesh. I call allgather() before setting up the point
locator.
Hmm... it's possible this is our bug, then. There were bugs in a
couple "DistributedMesh, but currently serialized" co
>
> ReplicatedMesh or DistributedMesh?
>
I'm using DistributedMesh. I call allgather() before setting up the point
locator.
Any chance you can set up a case we can try to replicate locally?
>
I will try making a test case that's crashing.
Thanks,
Harshad
On Wed, 2 Aug 2017, Harshad Sahasrabudhe wrote:
I'm using version 1.1. The crash only happens with 2 or more
processes. It doesn't happen on a single process.
ReplicatedMesh or DistributedMesh?
Any chance you can set up a case we can try to replicate locally?
---
Roy
---
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
wrote:
>
> On Tue, 1 Aug 2017, Harshad Sahasrabudhe wrote:
>
> I got a segfault when I called the PointLocatorTree:
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
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,
> Hars
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
Hello,
I got a segfault when I called the PointLocatorTree::operator() function.
Does anyone know why the segfault? Thanks! Here's the backtrace:
(gdb) bt
#0 0x2aaffd5a5e7b in libMesh::TreeNode<8u>::find_element
(this=0x5a6f810,
p=..., allowed_subdomains=0xd6, relative_tol=9.