-
Notifications
You must be signed in to change notification settings - Fork 18.1k
runtime: VirtualAlloc of 1048576 bytes failed with errno=487 #14638
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
The code is closed source. |
Please show me small code that can reproduce. |
I don't think there is anything that can be done. Virtual address space on windows/386 is very limited and the program you are trying to build is simply too big. Are you able to use a 64bit platform ? |
I will try it on 64bit later. |
The program you're trying to link is just too big
for 32-bit toolchain.
Even if you're building 32-bit binaries, if you're
using 64-bit windows, try using the 64-bit tool
chain.
|
errno=487 is ERROR_INVALID_ADDRESS. I wonder why calling VirtualAlloc here returns ERROR_INVALID_ADDRESS. Alex |
I run it on 64bit and is ok. |
Please answer these questions before submitting your issue. Thanks!
go version
)?go version go1.6 windows/386
go env
)?set GOARCH=386
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=386
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\tpt_programs\go_3td;C:\tpt_programs\Jenkins\jobs\xxx\workspace\src\engine
set GORACE=
set GOROOT=C:\tpt_programs\go
set GOTOOLDIR=C:\tpt_programs\go\pkg\tool\windows_386
set GO15VENDOREXPERIMENT=1
set CC=gcc
set GOGCCFLAGS=-m32 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
(Use play.golang.org to provide a runnable example, if possible.)
run 'go build' on the windows
Build is ok.
The text was updated successfully, but these errors were encountered: