Neil Robins wrote: > I had autosave enabled when I analysed this. I can't yet say whether > disabling autosave will solve the problem because reanalysing with it on > doesn't reproduce this error exactly. I suggest trying to reproduce this > sort of thing by playing a match with lots of moves that are > deliberately bad set to autosave as often as possible. > This sgf file comes from a match where the fourth move made was 8/2 6/2* > not the 24/18 22/18 GNU has changed it to, and clearly the rest of the > game only makes sense after what was actually played. >
Looking at the code now I see a potential problem with the movelist. I'll see if I can reproduce and fix it regardless. Christian. _______________________________________________ Bug-gnubg mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-gnubg
