Seems to be some sort of concurrency problem. I
thought this was gone, but it appears to still be a
problem. Really, what should happen is that we need to
implement the 'ping' command.
May have helped this problem by outputting the move to
Winboard after applying it to the internal board. Also fixed a
bug with pondering that arose if the engine attempted to
ponder on a move that causes a repetition draw no matter
what (when the king has only 1 option out of check).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Made another little small fix that could potentially help.
During the null move search, the capsqr field was not set to
-1 before the recursive call. This may have allowed a capsqr
of > -1 to percolate down without a corresponding capture
piece, which would cause a crash.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Logged In: YES
user_id=128504
May have helped this problem by outputting the move to
Winboard after applying it to the internal board. Also fixed a
bug with pondering that arose if the engine attempted to
ponder on a move that causes a repetition draw no matter
what (when the king has only 1 option out of check).
Logged In: YES
user_id=128504
Made another little small fix that could potentially help.
During the null move search, the capsqr field was not set to
-1 before the recursive call. This may have allowed a capsqr
of > -1 to percolate down without a corresponding capture
piece, which would cause a crash.