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
internal compiler error: Segmentation fault #22666
Comments
@MauroMombelli : could you post more precise instructions to reproduce? If I do:
I get |
That looks like a It seems like it's crashing on
Can you please post the full crash message? |
please look here. Let me know if the issue is from another repo |
@randall77 the full command is GOPATH="$srcdir" go get -fix -v -x github.com/google/cloud-print-connector/gcp-cups-connector where $srcdir is the current dir |
Step one, it was complaining that I needed |
full build step in https://github.com/google/cloud-print-connector/wiki/Build-from-source please note the package im using is on arch linux full default installations; i can't assure you can reproduce under ubuntu or even arch derivatives |
Ok, that helps. Missing magic was |
gcc --version this is an huge difference :) |
I tried with gcc 7.2.0 and still I can't reproduce your error. @ianlancetaylor, is there any way to verify which gcc was actually used to make a cgo binary? I just put gcc 7.2.0 ahead in my path from the default gcc, but I don't know If that's sufficient. How does the BTW, gcc 7.2.0 took ~3 hours to build from scratch. make.bash doesn't seem so slow anymore... |
@MauroMombelli, perhaps you can prepare a Dockerfile showing the repro in a docker container? That is, give @randall77 the repro on a silver platter. |
I don't even have idea where to start to do something like this. I'll take
a look tomorrow but I can't promise nothing. As I can reproduce, maybe I
can run with gdb, but I'm fairly sure my binary come stripped..
…On Sat, Nov 11, 2017, 23:24 Brad Fitzpatrick ***@***.***> wrote:
@MauroMombelli <https://github.com/mauromombelli>, perhaps you can
prepare a Dockerfile showing the repro in a docker container? That is, give
@randall77 <https://github.com/randall77> the repro on a silver platter.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#22666 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AGE80TmKpDVqD_E31byspiEaPNJk4fEHks5s1h6GgaJpZM4QaDHx>
.
|
I still can easily get an internal compiler error with |
today I tried again (after switchng back to 1.8 yesterday, i re-uplaoded to 1.9.2) and the compilation completed successfully. I have no ideas. |
@randall77 You can see the version of GCC used to build a Go program that uses cgo by running Also, next time you have to build an old version of GCC add |
The segmentation fault was coming from the C compiler, not the Go compiler. It appears that the problem can not be recreated. I'm going to close this issue since I don't see anything we can do here. Please comment if you disagree. |
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?go version go1.9.2 linux/amd64
Does this issue reproduce with the latest release?
it is latest
What operating system and processor architecture are you using (
go env
)?GOARCH="amd64"
GOBIN=""
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/mauro/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build324052906=/tmp/go-build -gno-record-gcc-switches"
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"
What did you do?
trying to compile https://aur.archlinux.org/packages/gcp-cups-connector/ commit 428847ac80d2b9a19fc87f00afde4b9ae4d883aa
ps. I don't know go, but that is quite clearly a compiler bug
The text was updated successfully, but these errors were encountered: