[Lldb-commits] [lldb] [lldb] Implement basic support for reverse-continue (PR #99736)

[via lldb-commits]

jimingham wrote:

BTW, another reason I want to focus here on direction and not on explicitly stating "reverse continue" and "actual resume" is that a lot of "forward" motion in a debug session with reverse debugging capability is actually going to be going "forward" but using the "reverse" machinery, right?

One pretty common workflow will be: 
1) set a breakpoint and run backwards to hit it, 
2) then run 'forwards' to figure out what happened there in the past
    - so for instance do a "forward next" to the next but still in the past source line
3) realize that you stepped over a function you wanted to look at so you step 'backwards' from one point in the past to another (back to the function call you stepped over)

Most of the execution control logic should just know "forward" and "backwards", but then whether those are implemented by using the reverse debugging machinery or by allowing the program to run for realz will be know deeper in the execution control machinery - most likely governed by the thread plans.

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