-
Notifications
You must be signed in to change notification settings - Fork 105
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
Segmentation fault when running Sibernetic built on WSL2 #170
Comments
impossible to debug sibernetic so just reporting that this is an issue |
@clausagerskov how is it impossible to debug? |
i mean i dont know much about debugging segmentation faults in c++, so i should have said i dont know how to do it rather than its impossible |
i cant replicate this in 18.04 though on a different machine, might be an opencl issue since i was testing CUDA support in WSL2 |
Apparently OpenCL on NVIDIA GPUs is not supported on WSL so this is not expected to work |
would be cool if someone with an intel gpu could check if they can run sibernetic on it in WSL2 since it should be supported |
this is strange, it happens on my nvidia gpu machine whether or not cuda is installed, even with just intel opencl |
commented out the try catch that was obscuring the actual cause of the error. turns out its "No OpenCL devices were found" |
this also happens when running in a WSL2 backed docker container. |
also happens with hyper-v backed docker containers |
clinfo output from docker container: Platform Name Intel(R) OpenCL NULL platform behavior |
Tried building Sibernetic on Windows Subsystem for Linux 2 (Ubuntu 20.04).
The build succeeds but then when I try to run sibernetic using the usual ./Release/Sibernetic -f worm (or any other configuration file), I get a segmentation fault
The text was updated successfully, but these errors were encountered: