-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/compile: SEGV in go 1.8 compiler (gc.typecheck1) with go build #19323
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
Comments
Ian and others, are you able to get the gzipped archive? |
@bstarynk Yes, I was able to retrieve it, and I was able to recreate the problem. It's a crash-on-invalid. The crashing line is
The Go function Here is a smaller case that recreates the problem:
|
On it. |
CL https://golang.org/cl/37584 mentions this issue. |
Fixes golang#19323 Change-Id: I92d1bdefb15de6178a577a4fa0f0dc004f791904
Fixes golang#19323 Change-Id: I92d1bdefb15de6178a577a4fa0f0dc004f791904
Thanks a lot for being so responsive. |
CL https://golang.org/cl/39601 mentions this issue. |
Fixes #19323 Fixes #19638 (backport) Change-Id: I92d1bdefb15de6178a577a4fa0f0dc004f791904 Reviewed-on: https://go-review.googlesource.com/39601 Run-TryBot: Austin Clements <austin@google.com> Reviewed-by: Josh Bleecher Snyder <josharian@gmail.com> TryBot-Result: Gobot Gobot <gobot@golang.org>
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.8 linux/amd64
What operating system and processor architecture are you using (
go env
)?Linux/x86-64
Debian/Sid/x86-64
GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/ssdhome/basile/mygoworkspace:/ssdhome/basile/monimelt"
GORACE=""
GOROOT="/usr/local/go"
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="/usr/bin/gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build617532280=/tmp/go-build -gno-record-gcc-switches"
CXX="g++"
CGO_ENABLED="1"
PKG_CONFIG="pkg-config"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
What did you do?
If possible, provide a recipe for reproducing the error.
For some reason, I am not able to upload the faulty tarball via this interface.
Uploading monimelt-go-segv.tar.gz…
But I have installed that gzipped tar archive on http://gcc-melt.org/monimelt-go-segv.tar.gz
Its md5sum is c1036d5473fa30a3b23dbb72e6f6389f
It is a small file of 19234 bytes (less than twenty kilobytes)
and it is exactly the commit bstarynk/monimelt@507be38
Extract it into some directory
monimelt-go-segv
then the three commands
export GOPATH=$PWD/monimelt-go-segv
cd monimelt-go-segv
go build src/monimelt.go
gives (in a reproducible fashion)
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
I am a newbie, perhaps making newbie mistakes. I am expecting compiler error messages, not SEGV
What did you see instead?
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x58 pc=0x998773]
and the shown backtrace is indeed inside the Go compiler & runtime.
The text was updated successfully, but these errors were encountered: