Skip to content
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

cmd/go: panic when attempting to load a plugin on 1.11.4 #32752

Closed
wangzz719 opened this issue Jun 24, 2019 · 5 comments
Closed

cmd/go: panic when attempting to load a plugin on 1.11.4 #32752

wangzz719 opened this issue Jun 24, 2019 · 5 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@wangzz719
Copy link

What version of Go are you using (go version)?

$ go version
go version go1.11.4 linux/amd64

Does this issue reproduce with the latest release?

go1.12.4 works correctly

What operating system and processor architecture are you using (go env)?

go env Output
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/wangzhizhao/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/wangzhizhao/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/wangzhizhao/go/src/code.byted.org/ies/sensitive_marker/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build679397982=/tmp/go-build -gno-record-gcc-switches"

What did you do?

With go1.11.4, I use go module with vendor mode, and then I load a so build whith go1.11.4, then I got a panic: plugin was built with a different version of package net

What did you expect to see?

plugin .so could be correctly loaded.

What did you see instead?

panic plugin was built with a different version of package net

@AlexRouSg
Copy link
Contributor

Have you tried 1.11.11?

@wangzz719
Copy link
Author

Have you tried 1.11.11?

go1.11.11 got the same error.

@andybons andybons changed the title go1.11.4 plugin got panic while using go module: plugin was built with a different version of package net cmd/go: plugin got panic while using go module on 1.11.4 Jun 25, 2019
@andybons andybons changed the title cmd/go: plugin got panic while using go module on 1.11.4 cmd/go: panic when attempting to load a plugin on 1.11.4 Jun 25, 2019
@andybons
Copy link
Member

@wangzz719 is there a reason you’re stuck on 1.11 and have not upgraded to 1.12? It’s unlikely this will be fixed by the time 1.11 becomes unsupported a couple months from now.

@andybons andybons added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Jun 25, 2019
@andybons andybons added this to the Unplanned milestone Jun 25, 2019
@wangzz719
Copy link
Author

@wangzz719 is there a reason you’re stuck on 1.11 and have not upgraded to 1.12? It’s unlikely this will be fixed by the time 1.11 becomes unsupported a couple months from now.

In our workplace, a lot of projects still using 1.11 and try using the go module to manage dependency. I can have a try to persuade other workmates using go module with 1.12.

@andybons
Copy link
Member

Closing for now since modules support is improving with each release and 1.11 will be unsupported soon anyway.

@golang golang locked and limited conversation to collaborators Jun 25, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

4 participants