-
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
Commit 55df0ee causes runtime crash when compiled with MinGW-w64 on Windows 10. #5108
Comments
Can you give us some information about how you compiled it and what the compilation output and stockfish output was? |
I compiled it as I always do using the command, After experimenting on this I discovered that the problem only occurs when "-march=haswell" is included in CPPFLAGS. Something in the latest source is clobbering or interfering with the optimization setting "-march=haswell". |
Can you run this through gdb perhaps (if it is installed for you)? |
Upon examining the changes to src/nnue/network.cpp and src/uci.cpp I noticed a lot of changes to Embedding nnue. I wonder if those are the source of bug. Could it be the source isn't parsing the CPPFLAGS instruction properly? |
@jackL999 can you please give the entire output of what is shown on the terminal? |
You also have a typo in |
Yes, but those typos were only made here. They don't exist in the command line executed in the terminal window. That command is taken directly from the history file and has successfully executed the compilation of Stockfish source scores of times. |
…? |
from previous request, running gdb, I get Thread 1 received signal SIGSEGV, Segmentation fault. |
Compilation produces the following, Config: Flags: Testing config sanity. If this fails, try 'make help' ... make ARCH=x86-64-bmi2 COMP=mingw all |
I re-ran gdb with stockfish compiled using debug=yes Config: It produced the following output Thread 1 received signal SIGSEGV, Segmentation fault. |
I was able to get the latest commit 55df0ee to compile and execute on Windows without problems using MinGW64 on ARCH Linux. Running the command "stockfish.exe compiler" in Windows using the ARCH Linux build produces the following output, Stockfish dev-20240312-55df0ee0 by the Stockfish developers (see AUTHORS file) This means that the problem is likely with the winlibs.com MinGW64 compiler and not with the Stockfish source. It is odd though that every build using this compiler on source commits prior to 1a26d69 worked without any issues. |
@jackL999 btw the new comple uses 13.1 vs your original one was 13.2 ... Regarding winlibs, I recommend following the installation guide for windows from here https://github.com/official-stockfish/Stockfish/wiki/Developers#windows |
@jackL999 if you still have your original environment could you test if it compiles now successfully? |
Describe the issue
Using MinGW-w64 from winlibs.com (gcc 13.2) Stockfish crashes with a runtime fault. All previous Stockfish versions from commit 632f1c2 and before compile and run without any problems.
I successfully compiled and executed commit 55df0ee in Linux and Android (arm64-v8a and armeabi-v7a) without any issues. Only the Windows 10 version fails to execute after compilation.
Expected behavior
To run in Windows 10 without crashing.
Steps to reproduce
stockfish.exe bench 2048 2 13 default depth nnue
Anything else?
No response
Operating system
Windows
Stockfish version
Stockfish development commit 55df0ee (12/03/2024)
The text was updated successfully, but these errors were encountered: