-
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
runtime: hello world
build failure on windows/amd64 with go1.21.0
#61980
Comments
Hmm I'm not totally convinced this is a duplicate, the stack trace seems different. I tried to replicate it and the issue reported by #61975 has the exact same stacktrace on both linux and windows, which is different from the one here. |
@Nasfame it likely isn't. |
@jay4195 I'm unable to reproduce. Can you run with D:\env\Go\bin\go.exe build -x -o C:\Users\Wangzhiyuan\AppData\Local\JetBrains\GoLand2023.2\tmp\GoLand\___go_build_hello_go.exe -gcflags "all=-N -l" D:\code\go\hello\hello.go Also, can you try running the following to se if one of these replicate the issue? D:\env\Go\pkg\tool\windows_amd64\compile.exe -V=full
D:\env\Go\pkg\tool\windows_amd64\asm.exe -V=full
D:\env\Go\pkg\tool\windows_amd64\link.exe -V=full |
For the first command, I reproduced in my laptop like this.
For the second part of commands, I tried several times and it seems to work fine with me.
|
FYI 0xc0000005 is the code for an access violation Might not be related but I noticed your username is |
@mauri870 This laptop belongs to my company. The dot after my name is the my company abbr. I currently only found this problem under my company's laptop. If I change the |
@mauri870 if I remove '-gcflags "all=-N -l"', I could alse get crash like this.
|
I don't think it is related to the user name. I've created a local user named |
CC @golang/runtime. |
@dmitshur
|
@Nasfame C:\Users\xxx\AppData\Local is windows temp folder, so I think programs should have access to it. I changed the code to
|
@Nasfame By the way I notice that I open the VirtualizationBasedTechnology CSP of windows defender, It that releated to the problem? |
hello world
build failure on windows/amd64 with go1.21.0
@Nasfame Yes, I switch go version to 1.20.7, still got that problem.
|
@Nasfame It was generated by GoLand2023.2
I also tried your command in go 1.20.7
|
@Nasfame Yes, I can run |
@Nasfame I call IT support to remove the Symantec Endpoint Protection from my laptop, the issue disappeared. I reckoned that golang has conflict with the Symantec Endpoint Protection. |
closing as I don't think there's anything the go project can reasonably do. |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes. In maybe 5 times of go build produce one build crash on go 1.21.0.
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Compile:
What did you expect to see?
What did you see instead?
The text was updated successfully, but these errors were encountered: