Skip to content
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.

Sign up for GitHub

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

Jump to bottom

runtime: unexpected return pc for runtime.asmstdcall #40469

Open
chalkwu opened this issue Jul 29, 2020 · 5 comments
Open

runtime: unexpected return pc for runtime.asmstdcall #40469

chalkwu opened this issue Jul 29, 2020 · 5 comments
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows
Milestone
Unplanned

Comments

@chalkwu
Copy link

chalkwu commented Jul 29, 2020

When I install go1.13.14, it looks everything is ok. Finished successfully, path environment is added automatically. But when I check go version by typing "go version" in command terminal, something wrong. The exception is just the same as #40401
Please help.

What version of Go are you using (go version)?

1.13.14

$ go version
C:\Windows\System32>go version
Exception 0xc0000005 0x8 0x0 0x0
PC=0x0

runtime: unexpected return pc for runtime.asmstdcall called from 0x11
stack: frame={sp:0x144fd20, fp:0x144fd30} stack=[0x0,0x144ff30)
000000000144fc20:  00000000001effff  0000000000000400
000000000144fc30:  00000000001d0200  0203000000000000
000000000144fc40:  00000000001effff  0000000000000400
000000000144fc50:  0203000000000000  00000000000001e0
000000000144fc60:  0000000000000400  0000000000000400
000000000144fc70:  00000000001d0200  00000000001effff
000000000144fc80:  000000000144fcc0  000000000041857b 
000000000144fc90:  00000000001d0100  0203000000000000
000000000144fca0:  00000000001effff  0000000001459090
000000000144fcb0:  01e0010000000400  0000000000000000
000000000144fcc0:  000000000144fd20  0000000000030000
000000000144fcd0:  0000000001459090  0000000000000000
000000000144fce0:  0000000000000008  00000000001effff
000000000144fcf0:  0000000001459008  0000000000000005
000000000144fd00:  0000000002030000  000000000144fd68
000000000144fd10:  0000000001459090  000000000045d8ce 
000000000144fd20: <000000000144fd40 !0000000000000011
000000000144fd30: >0000000002030000  0000000002030000
000000000144fd40:  0000000000000020  0000000000b0efe8
000000000144fd50:  0000000001459090  0000000000000000
000000000144fd60:  0000000000e965a0  000000000144fd88
000000000144fd70:  0000000001459090  000000000144fe18
000000000144fd80:  000000000040c490   000000c000002000
000000000144fd90:  00000000000001e0  00000000000001e0
000000000144fda0:  0000000000e96828  000000000045b767 
000000000144fdb0:  0001fffffffffff8  00000000000001d8
000000000144fdc0:  00000000000001e0  000000c000002000
000000000144fdd0:  0000000001450008  000000000144fdf8
000000000144fde0:  0000000000000000  0000000001450008
000000000144fdf0:  0000000000000000  000000000042eb03 
000000000144fe00:  000000000045d870   0000000000e96828
000000000144fe10:  000000c000000000  000000000000000f
000000000144fe20:  0000000000e965a0  000000000144fe48
runtime.asmstdcall(0x2030000, 0x2030000, 0x20, 0xb0efe8, 0x1459090, 0x0, 0xe965a0, 0x144fd88, 0x1459090, 0x144fe18, ...)
        c:/go/src/runtime/sys_windows_amd64.s:60 +0x5e fp=0x144fd30 sp=0x144fd20 pc=0x45d8ce
rax     0x0
rbx     0xe96828
rcx     0xeb4980
rdi     0x37b000
rsi     0x144fe60
rbp     0x144fe28
rsp     0x144fd18
r8      0x4
r9      0x144fea0
r10     0x8
r11     0x1d010e
r12     0xb0efe8
r13     0x0
r14     0x0
r15     0x2030000
rip     0x0
rflags  0x10293
cs      0x33
fs      0x53
gs      0x2b

Does this issue reproduce with the latest release?

No.

What operating system and processor architecture are you using (go env)?

Window version: Windows Server 2016 Datacenter
Cpu: Intel(R) Xeon(R) Bronze 3106CPU @ 1.70GHz 1.70GHz
RAM: 128 GB
architecture: 64-bit

go env Output
$ go env

What did you do?

What did you expect to see?

go version go1.13.14 windows/amd64

What did you see instead?

unexpected....
@alexbrainman
Copy link
Member

Thank you @chalkwu for opening this issue.

Is your issue also duplicate of #21060 ? Perhaps you have too much memory in your computer, and Go cannot run on a machine with 128 GB of memory. Unfortunately I cannot check, because I don't have PC with so much memory. Try installing Go on PC with less memory, see if it works for you.

I don't think Go Team has Windows testing PC with so much memory. So I would not be surprised if it is broken.

/cc @aclements @mknyszek @cherrymui

Thank you.

Alex

@alexbrainman alexbrainman mentioned this issue Jul 29, 2020
Open
@ALTree ALTree added NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows labels Jul 29, 2020
@chalkwu
Copy link
Author

chalkwu commented Jul 30, 2020

Thank you @chalkwu for opening this issue.

Is your issue also duplicate of #21060 ? Perhaps you have too much memory in your computer, and Go cannot run on a machine with 128 GB of memory. Unfortunately I cannot check, because I don't have PC with so much memory. Try installing Go on PC with less memory, see if it works for you.

I don't think Go Team has Windows testing PC with so much memory. So I would not be surprised if it is broken.

/cc @aclements @mknyszek @cherrymui

Thank you.

Alex

Thank you so much. By the way, how did you find there is another issue which is just the same as this one.

@alexbrainman
Copy link
Member

how did you find there is another issue which is just the same as this one.

I don't remember how I found related issue.

Alex

@mt-mithril
Copy link

I have tested on an 128g ram server and I successfully reproduced the problem. I tried to compile a 32bit version and it succeed. I think the reason for this problem may related to wrong CPU settings in bios like Virtualization settings, etc. I hope this can help you!

@networkimprov networkimprov mentioned this issue Aug 3, 2020
Open
@networkimprov
Copy link

cc @jstarks for any insights...

@alexbrainman alexbrainman mentioned this issue Aug 31, 2020
Closed
@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Jul 7, 2022
@mknyszek mknyszek moved this to Triage Backlog in Go Compiler / Runtime Jul 15, 2022
@rsc rsc mentioned this issue Aug 5, 2022
Closed
@seankhliao seankhliao added this to the Unplanned milestone Aug 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
compiler/runtime Issues related to the Go compiler and/or runtime. NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. OS-Windows
Projects
Go Compiler / Runtime
Status: Triage Backlog
Milestone
Unplanned
Development

No branches or pull requests
7 participants
@networkimprov @ALTree @gopherbot @alexbrainman @seankhliao @mt-mithril @chalkwu