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 trying to work around some issues with the current implementation of encoding/asn1 by taking a copy of the go files for this package and creating a my own package of them that I can then update. However I get different behaviour using these source files, even when I make no changes to them, than I do with the built go binary.
I copy these source files to my own package directory, make no changes and update the code that uses them to import this location instead for asn1 functionality.
This code can demonstrate this: https://play.golang.org/p/I5EfVpw10y
The code path using "encoding/asn1" generates a different output to identical copy of the asn1 source code.
What version of Go are you using (
go version
)?go version go1.7.5 linux/amd64
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GORACE=""
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build372878858=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1
Issue
I have been trying to work around some issues with the current implementation of encoding/asn1 by taking a copy of the go files for this package and creating a my own package of them that I can then update. However I get different behaviour using these source files, even when I make no changes to them, than I do with the built go binary.
I copy these source files to my own package directory, make no changes and update the code that uses them to import this location instead for asn1 functionality.
This code can demonstrate this: https://play.golang.org/p/I5EfVpw10y
The code path using "encoding/asn1" generates a different output to identical copy of the asn1 source code.
So it seems that the source that is distributed as part of 1.7.5 is not what the binary was built from. Or have I got something wrong here?
The text was updated successfully, but these errors were encountered: