Skip to content
New issue

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

runtime: frequent SIGSEGV in readgstatus in bootstrap toolchain #55304

Open
cherrymui opened this issue Sep 21, 2022 · 0 comments
Open

runtime: frequent SIGSEGV in readgstatus in bootstrap toolchain #55304

cherrymui opened this issue Sep 21, 2022 · 0 comments
Assignees
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Milestone

Comments

@cherrymui
Copy link
Member

cherrymui commented Sep 21, 2022

Spilt off from #49686 to be clear about the current issue with the bootstrap toolchain and not to be confused with the old bug.

The original bug in #49686 has been fixed in Go 1.18. We are currently using Go 1.17 as the bootstrap toolchain which doesn't contain the fix, and we still occasionally see the failure.

It seems the current decision is to wait and see if more failures come up and see whether it is the bootstrap toolchain's issue. Then we can make a decision, e.g. backporting the fix, or bumping the bootstrap version.

cc @mknyszek @rsc @bcmills

@gopherbot gopherbot added the compiler/runtime Issues related to the Go compiler and/or runtime. label Sep 21, 2022
@cherrymui cherrymui added WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. and removed compiler/runtime Issues related to the Go compiler and/or runtime. labels Sep 21, 2022
@cherrymui cherrymui added this to the Go1.20 milestone Sep 21, 2022
@cherrymui cherrymui added the NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. label Sep 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
NeedsInvestigation Someone must examine and confirm this is a valid issue and not a duplicate of an existing one. WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

3 participants