-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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/trace: frame pointer unwinding crash on arm64 during async preemption [1.21 backport] #65449
Comments
Change https://go.dev/cl/560735 mentions this issue: |
There is technically a workaround here: setting Therefore in my opinion we should either backport this fix, or backport a change to set |
The fix was merged in October, so I feel fairly confident that it's safe at this point. It's also pretty small. I'm inclined to approve this. |
…tore in epilogue For leaf but nonzero-frame functions. Currently we're not restoring it properly. We also need to restore it before popping the stack frame, so that the frame won't get clobbered by a signal handler in the meantime. For #63830 Fixes #65449 Needs a test, but I'm not at all sure how we would actually do that. Leaving for inspiration. Change-Id: I273a25f2a838f05a959c810145cccc5428eaf164 Reviewed-on: https://go-review.googlesource.com/c/go/+/538635 Reviewed-by: Cherry Mui <cherryyz@google.com> Reviewed-by: Eric Fang <eric.fang@arm.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: David Chase <drchase@google.com> (cherry picked from commit c9888bd) Reviewed-on: https://go-review.googlesource.com/c/go/+/560735 TryBot-Bypass: Michael Knyszek <mknyszek@google.com> Reviewed-by: Keith Randall <khr@golang.org>
Closed by merging 2fdad8a to release-branch.go1.21. |
@prattmic requested issue #63830 to be considered for backport to the next 1.21 minor release.
The text was updated successfully, but these errors were encountered: