yade-dev team mailing list archive
-
yade-dev team
-
Mailing list archive
-
Message #10859
Re: [Bug 1314736] Re: Segfault possibly in new parallel collider
2014-05-21 15:29 GMT+02:00 Bruno Chareyre <1314736@xxxxxxxxxxxxxxxxxx>:
> :)
> Maybe the warning should be "consider turning collider.ompThreads=1" instead of "consider turning ompThreads=1"?
Yes, you are right. Because it looks like to switch off parallel mode
for the whole simulation.
Anton
--
You received this bug notification because you are a member of Yade
developers, which is subscribed to Yade.
https://bugs.launchpad.net/bugs/1314736
Title:
Segfault possibly in new parallel collider
Status in Yet Another Dynamic Engine:
Fix Released
Bug description:
I have got segfault, which is probably due to a new parallel collider.
It happened on my "local" version, which is not yet merged to the main
branch [1] (with ENABLE_LIQCONTROL=ON option), but it is unlikely due
to my changes.
Before the crash I have got the following warning several times:
ERROR /home/gladk/dem/yade/trunk/pkg/common/InsertionSortCollider.cpp:132 insertionSortParallel: parallel sort not guaranteed to succeed; in chunk 1 of 2, bound descending past half-chunk. Consider turning ompThreads=1 for thread safety.
....
....
Segmentation fault
I will try to provide the minimal script, which produces such
segfault. Bruno, maybe you have an idea, where it crashes?
[1] https://github.com/gladk/trunk
Thanks
Anton
To manage notifications about this bug go to:
https://bugs.launchpad.net/yade/+bug/1314736/+subscriptions
References