History log of /external/lldb/test/benchmarks/stepping/TestRunHooksThenSteppings.py
Revision Date Author Comments (<<< Hide modified files) (Show modified files >>>)
5f2ed17114c1711a23011c160832b318d77db888 20-Oct-2011 Johnny Chen <johnny.chen@apple.com> Parameterize the iteration count used when running benchmarks, instead of hard-coded inside the test case.
Add a '-y count' option to the test driver for this purpose. An example:

$ ./dotest.py -v -y 25 +b -p TestDisassembly.py

...

----------------------------------------------------------------------
Collected 2 tests

1: test_run_gdb_then_lldb (TestDisassembly.DisassembleDriverMainLoop)
Test disassembly on a large function with lldb vs. gdb. ...
gdb benchmark: Avg: 0.226305 (Laps: 25, Total Elapsed Time: 5.657614)
lldb benchmark: Avg: 0.113864 (Laps: 25, Total Elapsed Time: 2.846606)
lldb_avg/gdb_avg: 0.503146
ok
2: test_run_lldb_then_gdb (TestDisassembly.DisassembleDriverMainLoop)
Test disassembly on a large function with lldb vs. gdb. ...
lldb benchmark: Avg: 0.113008 (Laps: 25, Total Elapsed Time: 2.825201)
gdb benchmark: Avg: 0.225240 (Laps: 25, Total Elapsed Time: 5.631001)
lldb_avg/gdb_avg: 0.501723
ok

----------------------------------------------------------------------
Ran 2 tests in 41.346s

OK


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@142598 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/benchmarks/stepping/TestRunHooksThenSteppings.py
8f8345fe26363c21ab9c04ddc25884a342ca15dd 20-Oct-2011 Johnny Chen <johnny.chen@apple.com> Remove stale code.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@142595 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/benchmarks/stepping/TestRunHooksThenSteppings.py
644ad087128da16a5533b3ce6cf0fb0cbaebb722 19-Oct-2011 Johnny Chen <johnny.chen@apple.com> Modify lldbtest.Base.runHooks() to now take the following keyword arguments:

child=None, child_prompt=None, use_cmd_api=False

By default, expect a pexpect spawned child and child prompt to be
supplied (use_cmd_api=False). If use_cmd_api is true, ignore the child
and child prompt and use self.runCmd() to run the hooks one by one.

Modify existing client to reflect the change.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@142532 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/benchmarks/stepping/TestRunHooksThenSteppings.py
5f3c567ea3bcd789ee4cd1f01fd38b816c5be46f 19-Oct-2011 Johnny Chen <johnny.chen@apple.com> Extract the run hooks functionality into the base class lldbtest.Base.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@142469 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/benchmarks/stepping/TestRunHooksThenSteppings.py
192871bcf6fe0881a0b0aface4306cb6ec93710e 12-Oct-2011 Johnny Chen <johnny.chen@apple.com> Add a more generic stepping benchmark, which uses the '-k' option of the test driver
to be able to specify the runhook(s) to bring the debug session to a certain state
before running the benchmarking logic. An example,

./dotest.py -v -t +b -k 'process attach -n Mail' -k 'thread backtrace all' -p TestRunHooksThenSteppings.py

spawns lldb, attaches to the 'Mail' application, does a backtrace for all threads, and then
runs the benchmark to step the inferior multiple times.


git-svn-id: https://llvm.org/svn/llvm-project/llvdb/trunk@141740 91177308-0d34-0410-b5e6-96231b3b80d8
/external/lldb/test/benchmarks/stepping/TestRunHooksThenSteppings.py