cmd/link: "corrupt input" fatal error with no further detail #15012
Comments
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 |
I've trigging this errors, It may be your develop environment has changed so you should delete your $GOPATH/pkg and build again. I guess. |
So much has changed since Go 1.6 that I'm going to close this bug. We never got reports of this from others and never saw it ourselves on our builders either. |
Version, Architecture: go1.6, linux/amd64
What did you do?
Interrupt a go build (possibly with
SIGKILL
), and then attempt to build again.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?
Or, with
-x
: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
$GOPATH/pkg
directory, but others might not easily find where the error message is coming from and determine what to do.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.
The text was updated successfully, but these errors were encountered: