Skip to content

runtime: missing frame sizes #5734

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

Closed
rsc opened this issue Jun 19, 2013 · 3 comments
Closed

runtime: missing frame sizes #5734

rsc opened this issue Jun 19, 2013 · 3 comments

Comments

@rsc
Copy link
Contributor

rsc commented Jun 19, 2013

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.
@alberts
Copy link
Contributor

alberts commented Jun 19, 2013

Comment 1:

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.

@alberts
Copy link
Contributor

alberts commented Jun 27, 2013

Comment 2:

issue #5797 points at 916cb45c0d5f, which went in on the same day as bb553699c7e6.

@rsc
Copy link
Contributor Author

rsc commented Jul 30, 2013

Comment 3:

I believe these are all fixed. If not, please open new bugs.

Status changed to Fixed.

@rsc rsc added fixed labels Jul 30, 2013
@rsc rsc self-assigned this Jul 30, 2013
@golang golang locked and limited conversation to collaborators Jun 24, 2016
@rsc rsc removed their assignment Jun 22, 2022
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants