You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would guess that the "unexpected return PC" is because the traceback code is getting confused by the switch to the gsignal stack in runtime.sigtramp in runtime/sys_darwin_arm64.s.
But there is a deeper problem which is that we should not have called gcWriteBarrier, which is what led to the traceback crash. The signal handler code should have a valid G and M, but it need not have a valid P. The call to gcWriteBarrier is only OK if there is a valid P. Since sighandler calls startpanic_m, startpanic_m can't have any write barriers. But it does.
So this is an actual occurrence of #26575, which I think I previously deduced just by reading the code. Closing this issue as a dup.
From https://build.golang.org/log/93c24b649dcf7c5e192159c4ab4288094a7a0582:
I failed to find an open issue for the crash.
The text was updated successfully, but these errors were encountered: