On Wed, Aug 23, 2017 at 12:37 PM, Greg Clayton <clayb...@gmail.com> wrote:
> This isn't a work around right? You should be triggering your reverse step > or reverse continue using a "process reverse-continue" or "thread > reverse-step" right? If you do this, everything will just work. There > should be no way this happens automagically without user interaction. Am I > missing something? > Wait a second... As far as I know, LLDB itself does not support reverse-debugging (unless I missed something in a major way). So there is no "process reverse-continue" command, is there? I am not talking about adding proper reverse-debugging to lldb. All I want to do is to hack together a script that emulates "process reverse-continue" in cases when remote target happens to support it. I'm sending commands directly to remote gdb via `process plugin packet send bs`, but that leaves lldb out of the loop because it does not analyze the response packet.
_______________________________________________ lldb-dev mailing list lldb-dev@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-dev
