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

[gopherbot]

@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.

[mknyszek]

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

[gopherbot]

Change https://golang.org/cl/309551 mentions this issue: [release-branch.go1.16] runtime: non-strict InlTreeIndex lookup in expandFinalInlineFrame

[gopherbot]

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