Skip to content

runtime/trace: segfault in runtime.fpTracebackPCs during deferred call after recovering from panic [1.20 backport] #62045

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

Closed
gopherbot opened this issue Aug 15, 2023 · 0 comments
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge

Comments

@gopherbot
Copy link
Contributor

@mknyszek requested issue #61766 to be considered for backport to the next 1.20 minor release.

@gopherbot Please open up a backport issue for Go 1.21.

This causes crashes that while rare (a fairly specific situation is required) are difficult to work around. The only option is turning off FP unwinding for the tracer, but that means a fairly severe regression in overheads, which can be a problem if you've already committed to tracing more frequently at scale. The fix is also small and fairly safe.

(This issue also does not apply to Go 1.20.)

@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Aug 15, 2023
@mknyszek mknyszek closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2023
@golang golang locked and limited conversation to collaborators Aug 14, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Projects
None yet
Development

No branches or pull requests

2 participants