We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
@cherrymui requested issue #38824 to be considered for backport to the next 1.16 minor release.
@gopherbot please backport this to previous releases. This can cause program that uses plugins to hang on macOS.
The text was updated successfully, but these errors were encountered:
Change https://golang.org/cl/373095 mentions this issue: [release-branch.go1.16] cmd/link: force eager binding when using plugins on darwin
[release-branch.go1.16] cmd/link: force eager binding when using plugins on darwin
Sorry, something went wrong.
This is a serious issue without a workaround.
[release-branch.go1.16] cmd/link: force eager binding when using plug…
5ef9566
…ins on darwin When building/using plugins on darwin, we need to use flat namespace so the same symbol from the main executable and the plugin can be resolved to the same address. Apparently, when using flat namespace the dynamic linker can hang at forkExec when resolving a lazy binding. Work around it by forcing early bindings. Updates #38824. Fixes #50245. Change-Id: I983aa0a0960b15bf3f7871382e8231ee244655f4 Reviewed-on: https://go-review.googlesource.com/c/go/+/372798 Trust: Cherry Mui <[email protected]> Reviewed-by: Than McIntosh <[email protected]> Reviewed-by: Ian Lance Taylor <[email protected]> Run-TryBot: Cherry Mui <[email protected]> TryBot-Result: Gopher Robot <[email protected]> (cherry picked from commit c5fee93) Reviewed-on: https://go-review.googlesource.com/c/go/+/373095
Closed by merging 5ef9566 to release-branch.go1.16.
No branches or pull requests
@cherrymui requested issue #38824 to be considered for backport to the next 1.16 minor release.
The text was updated successfully, but these errors were encountered: