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
from https://golang.org/issue/5723?c=12
We're also seeing a crash that looks like it might be related to:
https://code.google.com/p/go/source/detail?r=bb553699c7e6
Yesterday was a holiday, so I'll check again whether we're still seeing this later today.
My previous message:
We're seeing a crash that dvyukov suggested might be related to this CL.
runtime: unknown argument frame size for runtime.copy
fatal error: invalid stack
goroutine 0 [idle]:
runtime: unknown argument frame size for runtime.sigreturn
panic during panic
No stack trace beyond that.
I suspect it's happening in code with quite a deep stack that is using the copy builtin
on some memory mapped with syscall.Mmap.
The text was updated successfully, but these errors were encountered:
I can still reproduce this intermittently at tip. I'm happy to test any patches with
fixes or patches that add debug output to the runtime if that will help.
The text was updated successfully, but these errors were encountered: