segmention fault while upgrading from 1.20.6 to 1.22.3

[M.Tarkeshwar Rao]

Hi all,

As part of regular LCM activity we are doing GoLang LCM. Issue is:

This is to bring to your immediate attention that while doing golang LCM ,
we changed it to 1.22.3 but CI job failed on the same .
Upon debugging  application it was deduced that there may be memory issue.
But even after trying the same on different dev machines same issue occurred.
Trying locally also it is failing with same error.
This is application error applicaton Docker image building.
 
This is a blocker for us. Kindly help us deducing how to proceed further.
 
Error:
Step 41/72 : RUN make build-go GO_BUILD_TAGS=${GO_BUILD_TAGS} WIRE_TAGS=${WIRE_TAGS}
---> Running in 0c954cffd4a6
(re)installing /root/go/bin/wire-v0.5.0
go: downloading github.com/pmezard/go-difflib v1.0.0
go: downloading github.com/google/subcommands v1.0.1
go: downloading golang.org/x/tools v0.0.0-20190422233926-fe54fb35175b
generate go files
/root/go/bin/wire-v0.5.0 gen -tags oss ./pkg/server
panic: runtime error: invalid memory address or nil pointer dereference [recovered]
        panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x57fd2f]
 
goroutine 875 [running]:
go/types.(*Checker).handleBailout(0xc000d09800, 0xc00636fca8)
        /usr/local/go/src/go/types/check.go:367 +0x88

My query is that what should we do for this error. We need to revert back or move to another version.

Regards

Tarkeshwar

[Ian Lance Taylor]

Is there a way that we can recreate the problem?

Ian

[Edgar Madrigal]

Have you tried 1.21.x? Not sure if this is something that might happen only in 1.22.3?

[Brian Candler]

> /root/go/bin/wire-v0.5.0 gen -tags oss ./pkg/server

Is it running the binary "/root/go/bin/wire-v0.5.0 <args>" at this point? If so, it would seem to be a bug in that application. Debug as you would any other go program. In particular, try running it under the race detector.  You don't give any reference to where this code comes from, but I'm guessing it's https://github.com/google/wire (and I note there is now a v0.6.0 release of that)

As Ian says: if you want further help (either from golang-nuts or from the developer of the "wire" package), it's best if you can trim this down to a small standalone test case, which doesn't include any proprietary code which you are unwilling to share, but which reproduces the problem.