-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
cmd/go: go mod download
segfault on linux/arm within QEMU on WSL2
#53348
Comments
Please try with Go 1.18.3 first - your version is somewhat out of date and there have been numerous fixes since then. |
Same error:
|
Are you running go inside user mode qemu inside a docker container on windows with a WSL2 backend? |
Yes i'm running go inside a user mode qemu inside a docker with WSL2 backend. |
#1508 tracks actually supporting and testing user-mode qemu. Fixing that bug by adding a builder and making all tests pass would surely need to fix this problem as well, so I'm not sure that keeping more issues open is necessary. That issue already functions as an umbrella to track user-mode qemu support. |
go mod download
segfault on linux/arm within QEMU on WSL2
Given the I suggest escalating it to the QEMU maintainers. I agree that there isn't anything we can plausibly do on the Go side without a fix (and active maintainer) for #1508. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Run go mod download in Ubuntu22.04 with qemu 7.0 (http://ftp.de.debian.org/debian/pool/main/q/qemu/qemu-user-static_7.0+dfsg-7_amd64.deb) and get a segfault:
Note: This is was done in a Windows Docker environment with the WSL2 Kernel for docker. In a virtual machine running qemu, the go install ... crashes afterwards.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Just execute go mod download.
What did you expect to see?
Go mod download to download the packages
What did you see instead?
go mod download segfaulted.
The text was updated successfully, but these errors were encountered: