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.

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

runtime: "invalid pc-encoded table" throw caused by bad cgo traceback (expandFinalInlineFrames) [1.16 backport] #45482

gopherbot opened this issue Apr 9, 2021 · 3 comments


Copy link

@gopherbot gopherbot commented Apr 9, 2021

@prattmic requested issue #45480 to be considered for backport to the next 1.16 minor release.

@gopherbot please open a backport for 1.16 and 1.15. The only workaround is to change the C traceback engine, which isn't usually feasible. This is a follow-up CL for a previously missed case.

Copy link

@mknyszek mknyszek commented Apr 12, 2021

There's no feasible workaround to this in many cases and is generally a safe change; it only permits more valid behaviors.


Copy link

@gopherbot gopherbot commented Apr 12, 2021

Change mentions this issue: [release-branch.go1.16] runtime: non-strict InlTreeIndex lookup in expandFinalInlineFrame


Copy link

@gopherbot gopherbot commented May 4, 2021

Closed by merging ea0537f to release-branch.go1.16.


@gopherbot gopherbot closed this May 4, 2021
gopherbot pushed a commit that referenced this issue May 4, 2021

This is a follow-up to, which made the same change
in Frames.Next. The same logic applies here: a profile stack may have
been truncated at an invalid PC provided by cgoTraceback.
expandFinalInlineFrame will then try to lookup the inline tree and

The same fix applies as well: upon encountering a bad PC, simply leave
it as-is and move on.

For #44971
For #45480
Fixes #45482

Change-Id: I2823c67a1f3425466b05384cc6d30f5fc8ee6ddc
Reviewed-by: Michael Knyszek <>
Trust: Michael Pratt <>
(cherry picked from commit aad13cb)
Run-TryBot: Michael Pratt <>
Reviewed-by: Cherry Zhang <>
TryBot-Result: Go Bot <>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants