[Lldb-commits] [lldb] [lldb] Introduce ScriptedFrameProvider for real threads (PR #161870)

[via lldb-commits]

jimingham wrote:

> > the need for coroutine stack traces. I need to splice in additional stack frames in the middle of real, physical stack frames.
> 
> @vogelsgesang Have you considered writing a custom unwinder for this? If you want stack frames from which you can perform step operations, I think you _need_ to go down language-plugin-unwinder route. This is what we do for swift async functions (which have a lot of similarities to C++ coroutines).

When all the frames you care about are "real" frames in that they exist somewhere in program memory and are laid out - once you find them - like all the other frames, and it's just a matter of finding them, then the custom unwinder model does seem more appropriate.

That's not what this PR is providing, it's a way of saying "Don't look at these 5 native frames, look at this one shiny synthesized frame instead".

https://github.com/llvm/llvm-project/pull/161870