Hi, Roy --
This happens when constructing a 2D disc using
MeshTools::Generation::build_sphere() using Intel 10.1 compilers with
debugging flags. My experience is that the Intel compilers are more
picky about this kind of stuff than GNU.
Here is a stack trace:
Program received signal SIGFPE,
Under what conditions does this occur? I'm surprised if you're seeing
it for 2D meshes (where IIRC we build quadtrees instead of octrees)
and I'm surprised that I've never seen it for 1D meshes...
Sounds like a straightforward solution, though; someone want to glance
over and commit it?
---
Roy
