Skip to content
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.

Sign up for GitHub

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

Jump to bottom

runtime: runtime.Caller returns invalid zero frame [1.11 backport] #25041

Closed
gopherbot opened this issue Apr 24, 2018 · 4 comments
Closed

runtime: runtime.Caller returns invalid zero frame [1.11 backport] #25041

gopherbot opened this issue Apr 24, 2018 · 4 comments
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Milestone
Go1.11.6

Comments

@gopherbot
Copy link

@FiloSottile requested issue #24108 to be considered for backport to the next 1.10 minor release.

@gopherbot please open a backport tracking issue, as this is a 1.10 regression.
@gopherbot gopherbot added the CherryPickCandidate Used during the release process for point releases label Apr 24, 2018
@gopherbot gopherbot mentioned this issue Apr 24, 2018
Closed
@gopherbot gopherbot added this to the Go1.10.2 milestone Apr 24, 2018
@andybons andybons modified the milestones: Go1.10.2, Go1.10.3 Apr 27, 2018
@FiloSottile FiloSottile modified the milestones: Go1.10.3, Go1.10.4 Jun 7, 2018
@andybons andybons modified the milestones: Go1.10.4, Go1.10.5 Aug 24, 2018
@dmitshur dmitshur modified the milestones: Go1.10.5, Go1.10.6 Nov 1, 2018
@dmitshur
Copy link
Contributor

dmitshur commented Nov 1, 2018

Not fixed in master yet, so I've moved the milestone to Go 1.10.6.

@dmitshur dmitshur modified the milestones: Go1.10.6, Go1.10.7 Dec 13, 2018
@FiloSottile
Copy link
Contributor

Retargeting to 1.11.

@FiloSottile FiloSottile changed the title runtime: runtime.Caller returns invalid zero frame [1.10 backport] runtime: runtime.Caller returns invalid zero frame [1.11 backport] Dec 14, 2018
@FiloSottile FiloSottile modified the milestones: Go1.10.7, Go1.11.4, Go1.11.5 Dec 14, 2018
@randall77
Copy link
Contributor

This has been fixed at tip and will go out with 1.12. I think the CL is too complicated to backport, however. We may have to leave this unfixed in 1.11.

@katiehockman
Copy link
Contributor

Thanks for the update @randall77. I checked out the issue, and it doesn't seem like it falls under the category of a "serious problem with no workaround" either. I'm going to close this backport issue, but please re-open if you feel that's in error.

@julieqiu julieqiu modified the milestones: Go1.11.5, Go1.11.6 Jan 23, 2019
@golang golang locked and limited conversation to collaborators Jan 23, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
CherryPickCandidate Used during the release process for point releases FrozenDueToAge
Projects
None yet
Milestone
Go1.11.6
Development

No branches or pull requests
7 participants
@andybons @FiloSottile @dmitshur @julieqiu @randall77 @gopherbot @katiehockman