You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
$ go version
go version devel +15f7a66 Tue May 3 14:57:06 2016 +0000 darwin/amd64
What did you do?
go build -o /tmp/command ./cmd/command
What did you expect to see?
I expected the package to compile and link successfully, as it does with go1.5.4 and go1.6.2.
What did you see instead?
cmd/compile panicked. Within my (closed-source) project, there are two packages that cause a panic in compile. One of them is a main package, the other a non-main package.
I eliminated lines in those two packages until the panic went away—the critical lines in both packages were a call to functions in a third (non-main) package that 1) successfully compiles, and 2) contains other functions with similar signatures that are called from elsewhere in the project without causing compiler panics.
I bisected the Go toolchain, which indicated 7538b1d—enabling the binary export format—as the first commit with this bug. Adding -gcflags="-newexport=0" to the command line when compiling with 15f7a66 results in a successful build.
It's not (yet) much to go on, particularly since I'm not able to share the code. What information would be most useful for debugging?
@rhysh Can you please confirm that this still crashes with the latest tip (I have fixed another import bug today, and I'm about to fix another one, likely). Thanks.
Thanks @griesemer , it looks like this is fixed. I'm unable to reproduce the crash with 2e32efc (go version devel +2e32efc Fri May 6 05:50:02 2016 +0000 darwin/amd64)
go build -o /tmp/command ./cmd/command
I expected the package to compile and link successfully, as it does with go1.5.4 and go1.6.2.
cmd/compile panicked. Within my (closed-source) project, there are two packages that cause a panic in compile. One of them is a main package, the other a non-main package.
I eliminated lines in those two packages until the panic went away—the critical lines in both packages were a call to functions in a third (non-main) package that 1) successfully compiles, and 2) contains other functions with similar signatures that are called from elsewhere in the project without causing compiler panics.
I bisected the Go toolchain, which indicated 7538b1d—enabling the binary export format—as the first commit with this bug. Adding
-gcflags="-newexport=0"
to the command line when compiling with 15f7a66 results in a successful build.It's not (yet) much to go on, particularly since I'm not able to share the code. What information would be most useful for debugging?
The text was updated successfully, but these errors were encountered: