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.gopark called from 0x1 #19955
Comments
This might've already been fixed in Go 1.8. Could you try Go 1.8.1? |
@t57root does this appear in Go 1.8? |
Sorry about the late reply. According to my experience so far, seems it doesn't appear in Go 1.8. because it's not inevitable. |
We generally only backport security issues. We've occasionally backported runtime crashes, so this might qualify, but it's not clear it's affecting enough people to be worth it. We'd encourage you to use Go 1.8 instead. /cc @aclements for his opinion. |
I agree with @bradfitz that this doesn't seem to qualify for a backport. Lots of things were fixed in 1.8, so we'd much rather users move forward (or tell us if there's an issue in Go preventing them for doing so!). Closing for now, but if you disagree or discover that you can reproduce it with 1.8, please comment and we'll reopen. |
Hi, @bradfitz @aclements I am using Go 1.9.2 and I got the same error as OP after several billion runs of a Go program. I happen to have the core dump, which I can send you in private if you wish to analyze it further. Please let me know, thanks. |
@guidovranken Can you show us the stack trace? I'd like to see if this looks like the same issue or a different one. Note that one error after several billion runs could easily be a random memory failure. Even if the bug is in Go if it takes several billion runs to repeat the problem we are unlikely to be able to fix it. |
@ianlancetaylor due to reasons I only have this screenshot of the original crash: https://i.imgur.com/mvMj24y.png In case it is relevant, the Go program was compiled as a static library and launched from a C++ program (a fuzzer actually, hence the billions of runs). |
What version of Go are you using (
go version
)?go version go1.7.4 linux/amd64
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/root/workspace/zagen/src/zagen/../../"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build295860934=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
What did you do?
I use signal.Notify() to get a channel to notify me when SIGTERM/SIGINT occurred. But when I hit ctrl+c(which produce SIGINT), the program sometimes crashed, showing
runtime: unexpected return pc for runtime.gopark called from 0x1
. This error seems happened conditionally, not inevitably.It's a large project and I don't know where exactly caused this problem. I kinda think such low-level error should not be caused by my user code. Here's the callstack printed automatically:
The text was updated successfully, but these errors were encountered: