-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lots of issue about position fen
and go
command
#5131
Comments
"Crashing" is definitely not the correct behavior to have here. Erroring out would be a possibility, FEN sanitizing has been a long-time discussion in issues, and a PR is currently open that addresses this: #4563 |
So now the problem is in searching algorithm, exactly generating legal moves. |
This is not a matter of search (nor move generation), by definition you can't have legal moves in an illegal position, especially one without pieces, the correct solution as already pointed out would be to refuse to parse the fen, long before the movegen or the search get called. |
This has nothing to do with the search algorithm. The UCI protocol assumes that every position/move sent by the GUI is valid, and the PR I mentioned earlier fixes this by not accepting illegal positions. The search isn't at fault here, the UCI handler is the one responsible. |
to be handled by 4563 |
Describe the issue
d
command shows information about tablebases at that positiongo
command still showbestmove a1a2 ponder a1b1
Expected behavior
Expected: crashes
Steps to reproduce
Anything else?
Stockfish 16:
Operating system
Windows
Stockfish version
Stockfish 16.1
The text was updated successfully, but these errors were encountered: