As was guessed by Son in a separate email the function is_infinite() in [1] gives the segfault randomly (~50% of the cases). When the it does not segfault the output is correct. When it segfaults it starts with the very same sequence of operations (e.g. the cells are visited in the same order) until the segfault occurs. It seems to be another compiler/cgal a-logical bug, reminiscent of [2]. B
[1] https://github.com/yade/trunk/blob/master/pkg/pfv/TwoPhaseFlowEngine.hpp#L360 [2] https://bugs.launchpad.net/yade/+bug/1666339 ** Changed in: yade Assignee: (unassigned) => Bruno Chareyre (bruno-chareyre) ** Changed in: yade Importance: Undecided => Medium ** Changed in: yade Status: New => Confirmed -- You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. https://bugs.launchpad.net/bugs/1732210 Title: getNeighbors_Segmentation fault (core dumped) Status in Yade: Confirmed Bug description: Hi, I got an error "Segmentation fault (core dumped)". I have narrowed down to find out that the problem is about the function getNeighbors(). But this error does not always happen. I got error when num_spheres = 50,100,200,250,300 but when num_spheres = 150 there will be no error with getNeighbors() My system info: Ubuntu 14.04 LTS Yade is compiled using packaged version yade-2017.01a Regards, Son To manage notifications about this bug go to: https://bugs.launchpad.net/yade/+bug/1732210/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~yade-dev Post to : yade-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~yade-dev More help : https://help.launchpad.net/ListHelp
