mirror of
https://github.com/HChaZZY/Stockfish.git
synced 2025-12-22 10:06:26 +08:00
Fix errouneus reset of ss->threatMove
After we set ss->threatMove we could go under a IID step that resets SearchStack ss and so also ss->threatMove. When later we use that field in futility pruning we have this set to MOVE_NONE ! The fix is to use a local variable and add threatMove to SplitPoint to pass this move to slaves. Spotted by Ralph Stoesser, fix suggested by Richard Vida. Signed-off-by: Marco Costalba <mcostalba@gmail.com>
This commit is contained in:
@@ -51,7 +51,6 @@ struct EvalInfo;
|
||||
struct SearchStack {
|
||||
Move currentMove;
|
||||
Move mateKiller;
|
||||
Move threatMove;
|
||||
Move excludedMove;
|
||||
Move bestMove;
|
||||
Move killers[2];
|
||||
|
||||
Reference in New Issue
Block a user