cherrymui

[2022-07-25T14:31:12-6ec939a-64f2829/openbsd-386-68](https://build.golang.org/log/2d05a66df32286ad4787645576be8f01092cb44f) [2022-07-21T22:58:07-ec1f924-076c3d7/openbsd-amd64-68](https://build.golang.org/log/23a227110fdca68bae271492bb0893cd113a6659) This is in TestServe but the failure is quite similar ``` --- FAIL: TestServe (1.24s) --- FAIL: TestServe/tcp (0.12s) serve_test.go:137: close tcp 127.0.0.1:40864: use of closed network connection...

Hi Filippo, The permission is granted. Thanks. See also #55841 . We are also considering give may-forge-author permission to approves, and update the git-codereview tool to prevent misuse. Thanks.

Is there a real need for such large number of sections? Or this is just an artificial example? Thanks.

Thanks. One possible answer is to reject a file with too many sections. cc @golang/compiler

Could you explain more about the problem of importing the reflect package? What functions/variables, if not used, cannot be pruned by the linker? Thanks.

cc @griesemer

Thanks for the report and for looking into it! It would be interesting if Solaris has similar issue as the BSD bug. We saw some GC-related failures (like `marked free...

@jmpesp would it be possible to provide a few full logs of the failure? It is possible that the logs contain the addresses that can give a hint to the...

Is the corruption always on the ELF header? Is it on the same machine or on multiple machines? What the file system are you running on? Thanks.

Thanks. Frequent corruption on the ELF header is probably enough information. The ELF header is written by the linker only. The compiler and (most of) the Go command are unrelated....