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 regularly build and test our closed source projects with go tip. They had been running and testing fine until recently, when I started seeing some unexpected return pc panics.
I commented at #45702 (comment), but in hindsight that may have been a slightly different, although related, issue.
@cherrymui's fix in 731a015 stopped my minimized reproducer from crashing, but then when I rebuilt the primary project with go tip including that fix, I saw two new trampoline calls in the stack from different tests.
Two new panics related to golang.org/x/sys/unix.libc_munmap_trampoline+0x0000000000000005 and golang.org/x/sys/unix.libc_ioctl_trampoline+0x0000000000000005. I assume this needs to be fixed beyond just those two cases, but those are the first two I've hit in our codebase.
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
n/a
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I regularly build and test our closed source projects with go tip. They had been running and testing fine until recently, when I started seeing some
unexpected return pc
panics.I commented at #45702 (comment), but in hindsight that may have been a slightly different, although related, issue.
@cherrymui's fix in 731a015 stopped my minimized reproducer from crashing, but then when I rebuilt the primary project with go tip including that fix, I saw two new
trampoline
calls in the stack from different tests.It looks like the existing use of
funcPC
at e.g. https://github.com/golang/sys/blob/0981d6026fa6241c75c6949829b5bd7a2574ad55/unix/zsyscall_darwin_amd64.go#L690 ought to also switch tointernal/abi.FuncPCABI0
(maybe?), but I am not sure whether x/sys is allowed to call into internal/abi. Nor am I sure whether that is the appropriate fix.What did you expect to see?
Tests passing.
What did you see instead?
Two new panics related to
golang.org/x/sys/unix.libc_munmap_trampoline+0x0000000000000005
andgolang.org/x/sys/unix.libc_ioctl_trampoline+0x0000000000000005
. I assume this needs to be fixed beyond just those two cases, but those are the first two I've hit in our codebase.One runtime stack for ioctl
One runtime stack for munmap
The text was updated successfully, but these errors were encountered: