Join GitHub today
runtime: fix wrapper elision when mid-stack inlining #28640
When we print a stack trace we skip wrapper functions, as they aren't user code so they might confuse users.
The current behavior is that if the outermost frame is a wrapper, all the user frames inlined into it are not printed (unless the wrapper function is the first in the stack trace, which is a special case).
We really need to base the print/noprint decision on logical frames, not real frames.
CL 147361 has a band-aid fix for a test that fails because of this issue.