================
@@ -158,7 +158,7 @@ class LLDB_API SBProcess {
lldb::SBError Destroy();
- lldb::SBError Continue();
+ lldb::SBError Continue(RunDirection direction = RunDirection::eRunForward);
----------------
jimingham wrote:
I think it should be possible for most of lldb not to care which direction we
happen to be going in. We just need to know the current direction, or the
intended direction of the active thread plan. If we have to start putting in
lots of special purpose logic for forward and backward outside of the
ProcessGDBRemote plugin, I think we're doing it wrong.
But that's going to be harder to do if we start having a bunch of forward and
reverse specific functions, since they all act as sites where you forget the
"current direction" and then have to re-infer it later on. It's particularly
awkward having some take a direction and some be special purpose forward or
backward.
https://github.com/llvm/llvm-project/pull/99736
_______________________________________________
lldb-commits mailing list
lldb-commits@lists.llvm.org
https://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
