-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: version command hangs on Windows Server 2019 #44908
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
Comments
Have you already ruled out a antivirus? Cause Go is tested on server 2008/2012/2016 and I am running it on windows 10 20H2. |
I try now with Windows 2019 / Windows 2016 with go1.16 and observe this issue. I try to build with "go build -v" and in Windows 2019 and Windows 2016 not working with go1.16. I try with go1.15.8 and this working correctly. But after several attempts it remains stuck. Maybe exist regression in go1.16 with Windows support. Thanks. |
With GO version 1.13.15. From the next version, the problem exists. |
Did u find a solution for this ? Have a similiar issue #48059 |
Timed out in state WaitingForInfo. Closing. (I am just a bot, though. Please speak up if this is a mistake or you have the requested information.) |
Microsoft Windows [Version 10.0.17763.737]
(c) 2018 Microsoft Corporation. All rights reserved.
C:\Users\Administrator>go version
fatal: morestack on g0
Exception 0x80000003 0x0 0x0 0x20d421
PC=0x20d421
runtime.abort()
c:/go/src/runtime/asm_amd64.s:852 +0x1
runtime.morestack()
c:/go/src/runtime/asm_amd64.s:425 +0x2a
goroutine 1 [runnable, locked to thread]:
go/build.init()
c:/go/src/go/build/build.go:1040 +0x4fb
rax 0x17
rbx 0xb805b0
rcx 0xb805b0
rdi 0xd5d3caa000
rsi 0xc0000d17a0
rbp 0xc0000d18a8
rsp 0xc0000d1880
r8 0xc0000d1658
r9 0xc0000d17d0
r10 0x0
r11 0x246
r12 0x5
r13 0x1
r14 0x4
r15 0xffffffffffffffff
rip 0x20d421
rflags 0x212
cs 0x33
fs 0x53
gs 0x2b
C:\Users\Administrator>
GO version: go version go1.16 windows/amd64
Windows Server 2019 Version 1809 (OS Build 17763.737)
The text was updated successfully, but these errors were encountered: