https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104832
--- Comment #3 from Toolybird <toolybird at tuta dot io> --- Thanks for the quick patch! Things are a bit different now but unfortunately the problem persists. It appears there is an element of randomness to this problem as the list of affected object files has changed. Some have disappeared, some new news ones have appeared. Here's a diff of the list between my first run and now with your patch: gcc-build/x86_64-pc-linux-gnu/libgo/archive/.libs/zip.o gcc-build/x86_64-pc-linux-gnu/libgo/archive/zip.o -gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/bug.o -gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/clean.o +gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/cache.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/envcmd.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/get.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/help.o +gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/list.o +gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/load.o +gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/modcmd.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/modfetch.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/modget.o -gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/test.o +gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/modload.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/workcmd.o gcc-build/x86_64-pc-linux-gnu/libgo/cmd/go/internal/work.o -gcc-build/x86_64-pc-linux-gnu/libgo/crypto/.libs/x509.o -gcc-build/x86_64-pc-linux-gnu/libgo/crypto/tls.o -gcc-build/x86_64-pc-linux-gnu/libgo/debug/.libs/macho.o -gcc-build/x86_64-pc-linux-gnu/libgo/fmt.o -gcc-build/x86_64-pc-linux-gnu/libgo/go/ast.o +gcc-build/x86_64-pc-linux-gnu/libgo/golang.org/x/mod/modfile.o +gcc-build/x86_64-pc-linux-gnu/libgo/golang.org/x/tools/go/analysis/passes/printf.o +gcc-build/x86_64-pc-linux-gnu/libgo/go/.libs/build.o gcc-build/x86_64-pc-linux-gnu/libgo/html/.libs/template.o gcc-build/x86_64-pc-linux-gnu/libgo/html/template.o gcc-build/x86_64-pc-linux-gnu/libgo/image/gif.o gcc-build/x86_64-pc-linux-gnu/libgo/image/.libs/gif.o +gcc-build/x86_64-pc-linux-gnu/libgo/image/png.o gcc-build/x86_64-pc-linux-gnu/libgo/index/suffixarray.o -gcc-build/x86_64-pc-linux-gnu/libgo/.libs/fmt.o -gcc-build/x86_64-pc-linux-gnu/libgo/.libs/os.o gcc-build/x86_64-pc-linux-gnu/libgo/.libs/runtime.o -gcc-build/x86_64-pc-linux-gnu/libgo/.libs/syscall.o gcc-build/x86_64-pc-linux-gnu/libgo/net/http.o gcc-build/x86_64-pc-linux-gnu/libgo/net/.libs/http.o gcc-build/x86_64-pc-linux-gnu/libgo/net/.libs/mail.o gcc-build/x86_64-pc-linux-gnu/libgo/net/.libs/rpc.o gcc-build/x86_64-pc-linux-gnu/libgo/net/mail.o gcc-build/x86_64-pc-linux-gnu/libgo/net/rpc.o -gcc-build/x86_64-pc-linux-gnu/libgo/os.o -gcc-build/x86_64-pc-linux-gnu/libgo/syscall.o -gcc-build/x86_64-pc-linux-gnu/libgo/testing.o +gcc-build/x86_64-pc-linux-gnu/libgo/runtime/.libs/pprof.o +gcc-build/x86_64-pc-linux-gnu/libgo/runtime.o +gcc-build/x86_64-pc-linux-gnu/libgo/runtime/pprof.o gcc-build/x86_64-pc-linux-gnu/libgo/text/.libs/template.o -gcc-build/x86_64-pc-linux-gnu/libgo/text/template.o Is it possible that ASLR is a factor here? That was indeed the case for another bug fixed by Jakub last year [1] Thanks again. [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101407
