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.

Sign up for GitHub

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

Jump to bottom

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

Closed
gopherbot opened this issue Aug 15, 2023 · 0 comments
Closed

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

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

Comments

@gopherbot
Copy link

@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
@gopherbot gopherbot mentioned this issue Aug 15, 2023
Closed
@mknyszek mknyszek closed this as not planned Won't fix, can't repro, duplicate, stale Aug 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@mknyszek @gopherbot