bob wrote:That's not always good enough. History counters. Killer moves. Counter moves. etc all have an effect on move ordering, and hence GHI type problems.. Not to mention different moves will get reduced differently depending on where they appear in the move list.
To be absolutely sure, you should indeed clear those too. Killer is usually not an issue, though, as it is very local, and Ippolit-like engines even clear it during search, so that you can be sure killers are from sibblings only.
To reproduce the error I always load the game upto the position, not just the position itself; that should take care of the GHI stuff.
I would be surprised if Henk used history or counter-move heuristic.
Bug has not gone away. It crashed again this morning. I used winboard but have forgotten to use -debug option. So I clicked on ok and winboard exited. Position gone.
Henk wrote:Skipper crashed two times in last three days. Unfortunately it is difficult to reproduce for I already played a few tournaments and no crash happened.
Any (quick) methods to fix this ?
[I decided to test perft first. For instance compute Kiwipete(5). But no crash of course.]
Simple: look in the log of svn/git at what revision things worked fine and then do a bisect (yes you can also bisect with svn) until you'll find the bug.
Or just look at the diffs, then it is most of the time rather obvious which change introduced the bug.
Bug must have to do with changes of last week. So probably bug in magic bit boards implementation. But then perft should crash too and they haven't yet. Magic bit boards was not the only change of course.
Henk wrote:Skipper crashed two times in last three days. Unfortunately it is difficult to reproduce for I already played a few tournaments and no crash happened.
Any (quick) methods to fix this ?
[I decided to test perft first. For instance compute Kiwipete(5). But no crash of course.]
Crashes to crashes ...
Mmm sure is a tribute to David Bowie ..
(Planet earth is blue)
And there is nothing I can do
