You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have been consistently receiving a problem on windows where a float conversion using fmt.Sprintf leads to a runtime error, do not know if its a golang bug or a programmatic bug. It seems like an overflow to me.
Wasn't able to find previous reports for this issue, following is the backtrace.
C:\mygo\src\github.com\minio\mc>go version
go version go1.4.2 windows/amd64
C:\mygo\src\github.com\minio\mc>
C:\mygo\src\github.com\minio\mc>go env
set GOARCH=amd64
set GOBIN=
set GOCHAR=6
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=C:\mygo
set GORACE=
set GOROOT=c:\go
set GOTOOLDIR=c:\go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0
set CXX=g++
set CGO_ENABLED=1
The text was updated successfully, but these errors were encountered:
The problem appears to be an interface value on the stack with an invalid interface method pointer. That code is completely different in 1.5. I don't know what fixed it specifically. But I'm closing this issue since it is apparently fixed.
I have been consistently receiving a problem on windows where a float conversion using fmt.Sprintf leads to a runtime error, do not know if its a golang bug or a programmatic bug. It seems like an overflow to me.
Wasn't able to find previous reports for this issue, following is the backtrace.
The text was updated successfully, but these errors were encountered: