[Lldb-commits] [lldb] [lldb] Implement basic support for reverse-continue (PR #99736)
Med Ismail Bennani via lldb-commits
lldb-commits at lists.llvm.org
Fri Jul 19 23:43:25 PDT 2024
================
@@ -0,0 +1,79 @@
+import lldb
+import unittest
+from lldbsuite.test.lldbtest import *
+from lldbsuite.test.decorators import *
+from lldbsuite.test.gdbclientutils import *
+from lldbsuite.test.lldbreverse import ReverseTestBase
+from lldbsuite.test import lldbutil
+
+
+class TestReverseContinueBreakpoints(ReverseTestBase):
+ @add_test_categories(["dwarf"])
+ def test_reverse_continue(self):
+ target, process, initial_threads = self.setup_recording()
+
+ # Reverse-continue. We'll stop at the point where we started recording.
+ status = process.ReverseContinue()
+ self.assertSuccess(status)
+ self.expect(
+ "thread list",
+ STOPPED_DUE_TO_HISTORY_BOUNDARY,
+ substrs=["stopped", "stop reason = history boundary"],
+ )
+
+ # Continue forward normally until the target exits.
+ status = process.Continue()
+ self.assertSuccess(status)
+ self.assertState(process.GetState(), lldb.eStateExited)
+ self.assertEqual(process.GetExitStatus(), 0)
+
+ @add_test_categories(["dwarf"])
+ def test_reverse_continue_breakpoint(self):
+ target, process, initial_threads = self.setup_recording()
+
+ # Reverse-continue to the function "trigger_breakpoint".
+ trigger_bkpt = target.BreakpointCreateByName("trigger_breakpoint", None)
+ status = process.ReverseContinue()
+ self.assertSuccess(status)
+ threads_now = lldbutil.get_threads_stopped_at_breakpoint(process, trigger_bkpt)
+ self.assertEqual(threads_now, initial_threads)
+
+ @add_test_categories(["dwarf"])
+ def test_reverse_continue_skip_breakpoint(self):
+ target, process, initial_threads = self.setup_recording()
+
+ # Reverse-continue, skipping a disabled breakpoint at "trigger_breakpoint".
+ trigger_bkpt = target.BreakpointCreateByName("trigger_breakpoint", None)
+ trigger_bkpt.SetCondition("0")
+ status = process.ReverseContinue()
+ self.assertSuccess(status)
+ self.expect(
+ "thread list",
+ STOPPED_DUE_TO_HISTORY_BOUNDARY,
+ substrs=["stopped", "stop reason = history boundary"],
+ )
+
+ def setup_recording(self):
+ """
+ Record execution of code between "start_recording" and "stop_recording" breakpoints.
+
+ Returns with the target stopped at "stop_recording", with recording disabled,
+ ready to reverse-execute.
+ """
+ self.build()
+ target = self.dbg.CreateTarget("")
+ process = self.connect(target)
+
+ # Record execution from the start of the function "start_recording"
+ # to the start of the function "stop_recording".
+ start_recording_bkpt = target.BreakpointCreateByName("start_recording", None)
+ initial_threads = lldbutil.continue_to_breakpoint(process, start_recording_bkpt)
+ self.assertEqual(len(initial_threads), 1)
+ target.BreakpointDelete(start_recording_bkpt.GetID())
+ self.start_recording()
+ stop_recording_bkpt = target.BreakpointCreateByName("stop_recording", None)
+ lldbutil.continue_to_breakpoint(process, stop_recording_bkpt)
+ target.BreakpointDelete(stop_recording_bkpt.GetID())
+ self.stop_recording()
----------------
medismailben wrote:
This is ok, but you could have [stopped the process at entry](https://github.com/llvm/llvm-project/blob/main/lldb/test/API/python_api/debugger/TestDebuggerAPI.py#L74) to start the recording and have something like a [stop-hook](https://lldb.llvm.org/use/python-reference.html#writing-target-stop-hooks-in-python) to stop recording instead of using public breakpoints.
https://github.com/llvm/llvm-project/pull/99736
More information about the lldb-commits
mailing list