On Mon, 29 May 2017, motiv4u wrote:
I noticed the "Fix memory leaks" in the CVS-repository http://cvs.savannah.gnu.org/viewvc/gnubg/gnubg/?sortby=date#dirlist looking at the Diffs, since the ChangeLog wasn't that clear for me.
These are unrelated to your issue. I used a feature from recent versions of gcc (-fsanitize=address) to track another problem and as a side effect it revealed many memory leaks. I fixed some easy ones but many other remain.
The one from "analyze rolls" is not among them but limiting the analysis depth to 4 instead of 5 decreased its maximum cost by a factor of 21. That should be enough to prevent the kind off crash you experienced in practical usage.
There's no need for depth 5 ... and it is not available anymore: 4 is the max today. I don't know when or where it is changed, but is after May 12 and before May 29.
_______________________________________________ Bug-gnubg mailing list Bug-gnubg@gnu.org https://lists.gnu.org/mailman/listinfo/bug-gnubg
