Tim MisiakNew blog post about DbgRs, where we finally get to stack walking! Want to understand how stack walking works in debuggers and profilers? This post explains how module unwind info is used to walk stacks and display a stack trace.
https://www.timdbg.com/posts/writing-a-debugger-from-scratch-part-6/
Writing a Debugger From Scratch - DbgRs Part 6 - Stacks
(New to this series? Consider starting from part 1) At the end of the last post, DbgRs could finally set breakpoints. That was the last really critical feature needed for controlling execution of a program. Now that it can stop on an arbitrary function or code location, the next step is to find more information about the state of the program. In my opinion, the single most useful piece of information is the call stack, so that’s what this post will be about.
Vincent I.