cmd/link: nosplit stack overflow error when cross compiling in Go 1.5.1 #12764
Comments
I cannot reproduce this with go1.5.1:
I can successfully build the exe. I can even run it on linux. Reopen if you can provide more steps to try. Thank you. Alex |
@alexbrainman I re-ran the experiment on two machines and kept everything exactly the same as you have documented. Here are my findings:
|
I don't know. I don't have Windows 10 computers. Perhaps this bug is tickled by that. Alex |
I'm still working on isolating the issue. I was NOT able to reproduce the issue on Windows 10 Pro (i5) running in VirtualBox. |
I'm closing this issue after all. How the issue went away for me is a mystery to me, but for the record here is what I did on my machine following successful tests on other machines: 1.) Reinstall Go for Windows amd64 |
Please reopen this issue. I see a similar issue when cross compiling to GOOS=linux on macosx using go 1.5.1 It happens in the link step, AFAICT from using the -v option to go build. runtime.cgocallbackg: nosplit stack overflow |
The reflect.typelinks issue is fixed on tip by https://golang.org/cl/16932. @rrh: are you compiling with -N? The stack sizes you are reporting are too large. The values I see are cgocallbackg 88 |
I was using the -N flag. If I don't use it, the problem goes away. |
I'm getting the same error on Windows 10(i7). |
@Agnikay In general it doesn't help much to comment on a closed issue. Few people will see your comment. In this case, see #13431 . |
I was trying to cross compile my Go project on windows/amd64 for linux/386, but got a "nosplit stack overflow" error. I followed the instructions that are outlined here. With
GOOS=linux
andGOARCH=386
, mygo env
looks as follows:The code I tried to compile is a simple hello world
The complete error I got when running
go build
is:Other target configurations that did work are
GOOS=windows GOARCH=386
andGOOS=linux GOARCH=amd64
, butGOOS=linux GOARCH=386
does not work.The text was updated successfully, but these errors were encountered: