Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/link: "corrupt input" fatal error with no further detail #15012
Version, Architecture: go1.6, linux/amd64
What did you do?
Interrupt a go build (possibly with
What did you expect to see?
A successful build, or an error message telling me where the problem is and what to do.
What did you see instead?
In our build system that just showed up as "corrupt input", with no further context. I had to hunt for the message, it's coming from here. It was easy for me as an experienced developer to know that I should probably delete my
Unfortunately I cannot provide the corrupted input, I cannot trivially determine which file is causing the problem and it is in private code. I will keep my corrupted pkg directory around for a few days in case anyone wants me to check anything, but otherwise I presume it is not useful.
By the way, because of the origin of the error message I guess it could be that
I also note that the code is littered with