Backport approved for Go 1.14 (#39955) and 1.13 (this issue) based on the rationale in #39955 (comment).

@cherrymui You've sent a 1.14 backport CL for #39955. Are you able to send one for 1.13 (this issue) as well?

I could do that. But Go 1.13 is EOL soon, right? Probably not needed, then?

@cherrymui Yes, 1.13 will become unsupported once 1.15 is released, which should happen next month. However, both 1.14 and 1.13 are supported equally until then (see #34536 for more details), so if this issue is serious to warrant a backport, our backport policy says that it must be applied to both 1.13 and 1.14 (since the bug exists in both versions). If it's okay not to apply it to 1.13, then that means it's okay not to apply it to 1.14 either.

So, the next steps here are to create a backport CL for Go 1.13, or wait for now, or decide that this issue doesn't warrant being backported and users can wait for Go 1.15 to get the fix. Let us know what approach you think is best.

Okay, I'll make a CL, then. Thanks.

Change https://golang.org/cl/241978 mentions this issue: [release-branch.go1.13] cmd/link: fix GC data reading from shared library (attempt 2)

Go 1.13 is no longer supported per release policy, so this backport issue is no longer needed and can be closed.