summaryrefslogtreecommitdiffstats
path: root/lldb/examples/python/process_events.py
diff options
context:
space:
mode:
authorEnrico Granata <egranata@apple.com>2013-03-08 20:29:13 +0000
committerEnrico Granata <egranata@apple.com>2013-03-08 20:29:13 +0000
commitf58cececaaee321143b177a0d7cbbffddcbfea4c (patch)
treea488537dcc777a7b1b68c3a35b1618d2f94850c1 /lldb/examples/python/process_events.py
parent8106d8082c406b4c381cd0d9604835fc35b45990 (diff)
downloadbcm5719-llvm-f58cececaaee321143b177a0d7cbbffddcbfea4c.tar.gz
bcm5719-llvm-f58cececaaee321143b177a0d7cbbffddcbfea4c.zip
Initial checkin of a new project: LLDB Performance Testing Infrastructure
This is a very basic implementation of a library that easily allows to drive LLDB.framework to write test cases for performance This is separate from the LLDB testsuite in test/ in that: a) this uses C++ instead of Python to avoid measures being affected by SWIG b) this is in very early development and needs lots of tweaking before it can be considered functionally complete c) this is not meant to test correctness but to help catch performance regressions There is a sample application built against the library (in darwin/sketch) that uses the famous sample app Sketch as an inferior to measure certain basic parameters of LLDB's behavior. The resulting output is a PLIST much like the following: <?xml version="1.0" encoding="UTF-8"?> <!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd"> <plist version="1.0"> <array> <dict> <key>fetch-frames</key> <real>0.13161715522222225</real> </dict> <dict> <key>file-line-bkpt</key> <real>0.029111678750000002</real> </dict> <dict> <key>fetch-modules</key> <real>0.00026376766666666668</real> </dict> <dict> <key>fetch-vars</key> <real>0.17820429311111111</real> </dict> <dict> <key>run-expr</key> <real>0.029676525769230768</real> </dict> </array> </plist> Areas for improvement: - code cleanups (I will be out of the office for a couple days this coming week, but please keep ideas coming!) - more metrics and test cases - better error checking This toolkit also comprises a simple event-loop-driven controller for LLDB, similar yet much simpler to what the Driver does to implement the lldb command-line tool. llvm-svn: 176715
Diffstat (limited to 'lldb/examples/python/process_events.py')
-rwxr-xr-xlldb/examples/python/process_events.py2
1 files changed, 2 insertions, 0 deletions
diff --git a/lldb/examples/python/process_events.py b/lldb/examples/python/process_events.py
index ab1cff725e1..7978c33f166 100755
--- a/lldb/examples/python/process_events.py
+++ b/lldb/examples/python/process_events.py
@@ -184,6 +184,7 @@ def main(argv):
event = lldb.SBEvent()
if listener.WaitForEvent (options.event_timeout, event):
state = lldb.SBProcess.GetStateFromEvent (event)
+ print "event %s" % (lldb.SBDebugger.StateAsCString(state))
if state == lldb.eStateStopped:
if stop_idx == 0:
if launch_info:
@@ -203,6 +204,7 @@ def main(argv):
run_commands (command_interpreter, options.stop_commands)
stop_idx += 1
print_threads (process, options)
+ print "continuing process %u" % (pid)
process.Continue()
elif state == lldb.eStateExited:
exit_desc = process.GetExitDescription()
OpenPOWER on IntegriCloud