summaryrefslogtreecommitdiff
path: root/examples/python/step_and_print.py
diff options
context:
space:
mode:
authorDimitry Andric <dim@FreeBSD.org>2017-12-18 20:12:36 +0000
committerDimitry Andric <dim@FreeBSD.org>2017-12-18 20:12:36 +0000
commitef5d0b5e97ec8e6fa395d377b09aa7755e345b4f (patch)
tree27916256fdeeb57d10d2f3d6948be5d71a703215 /examples/python/step_and_print.py
parent76e0736e7fcfeb179779e49c05604464b1ccd704 (diff)
Notes
Diffstat (limited to 'examples/python/step_and_print.py')
-rw-r--r--examples/python/step_and_print.py24
1 files changed, 24 insertions, 0 deletions
diff --git a/examples/python/step_and_print.py b/examples/python/step_and_print.py
new file mode 100644
index 0000000000000..41364ef97ba84
--- /dev/null
+++ b/examples/python/step_and_print.py
@@ -0,0 +1,24 @@
+""" Does a step-over then prints the local variables or only the ones passed in """
+import lldb
+
+class StepAndPrint:
+ def __init__(self, debugger, unused):
+ return
+
+ def __call__(self, debugger, command, exe_ctx, result):
+ # Set the command to synchronous so the step will complete
+ # before we try to run the frame variable.
+ old_async = debugger.GetAsync()
+ debugger.SetAsync(False)
+
+ debugger.HandleCommand("thread step-over")
+ print("---------- Values: -------------------\n")
+ debugger.HandleCommand("frame variable %s"%(command))
+
+ debugger.SetAsync(old_async)
+
+ def get_short_help(self):
+ return "Does a step-over then runs frame variable passing the command args to it\n"
+
+def __lldb_init_module(debugger, unused):
+ debugger.HandleCommand("command script add -c step_and_print.StepAndPrint sap")