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
runtime: unexpected return pc for runtime.selectgo called from 0xXXX #25602
Comments
This looks like memory corruption. Have you tried running your program under the race detector? See https://blog.golang.org/race-detector . |
I get no data race report by using log1
log2
log3
|
Does this always fail in the same way? Is there any way that we can get the code to recreate the problem ourselves? |
I see some CGo in the code snippet. If it fails reliably, please try adding some runtime.KeepAlive calls after the C calls to ensure that this is not a lifetime/liveness problem. |
@ianlancetaylor The error message is same, but it's location is random. And these codes are for the company, i cannot provide them. |
@ianlancetaylor I can provide remote desktop to review codes. Is it ok? |
pmanage is deprecated, so close the issue. |
What version of Go are you using (
go version
)?go version go1.10.2 linux/amd64
Does this issue reproduce with the latest release?
YES
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOCACHE="/root/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/go"
GORACE=""
GOROOT="/opt/go"
GOTMPDIR=""
GOTOOLDIR="/opt/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
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-build250776484=/tmp/go-build -gno-record-gcc-switches"
What did you do?
run my binary
What did you expect to see?
no panic
What did you see instead?
log1:
/root/go/src/pmanage/manager.go:
log2:
/root/go/src/pmanage/util.go:
The text was updated successfully, but these errors were encountered: