Searched refs:dotest (Results 1 – 14 of 14) sorted by relevance
1 # Make lldb-dotest a custom target.2 add_custom_target(lldb-dotest)3 add_dependencies(lldb-dotest lldb-test-depends)4 set_target_properties(lldb-dotest PROPERTIES FOLDER "lldb utils")26 # Generate lldb-dotest Python driver script for each build mode.53 lldb-dotest.in54 ${config_runtime_output_dir}/lldb-dotest @ONLY65 lldb-dotest.in66 ${LLDB_DOTEST_DIR}/lldb-dotest75 lldb-dotest.in[all …]
4 - dotest.py7 directory and issue the './dotest.py' command or './dotest.py -v' for more8 verbose output. '.dotest.py -h' prints out the help messge.11 directory in order to be recognized by 'dotest.py' test driver as a module16 1. ./dotest.py -v . 2> ~/Developer/Log/lldbtest.log039 test case on its own. To run the whole test suite, 'dotest.py' is all you108 - dotest.pl110 In case you wonder, there is also a 'dotest.pl' perl script file. It was117 suite become more reliable, we don't expect to be using 'dotest.pl' anymore.119 Note: dotest.pl has been moved to the attic directory.[all …]
5 from . import dotest7 run_suite = dotest.run_suite
43 # Additional dotest arguments can be passed to lit by providing a44 # semicolon-separates list: --param dotest-args="arg;arg".45 dotest_lit_args_str = lit_config.params.get('dotest-args', None)
5 [11:31:19] johnny:/Volumes/data/lldb/svn/ToT/test $ ./dotest.py -A x86_64 -v -c ../examples/test/.l…8 [11:32:48] johnny:/Volumes/data/lldb/svn/ToT/test $ ./dotest.py -A x86_64 -v -c ../examples/test/.l…38 Command invoked: python ./dotest.py -A x86_64 -v -c ../examples/test/.lldb-pre-post-flight function…
9 [11:31:34] johnny:/Volumes/data/lldb/svn/ToT/test $ ./dotest.py -A x86_64 -v -c ../examples/test/.l…38 Command invoked: python ./dotest.py -A x86_64 -v -c ../examples/test/.lldb-loggings functionalities…70 [11:37:09] johnny:/Volumes/data/lldb/svn/ToT/test $ ./dotest.py -A x86_64 -v -c ../examples/test/.l…102 Command invoked: python ./dotest.py -A x86_64 -v -c ../examples/test/.lldb-loggings functionalities…
9 [15:36:32] johnny:/Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v -c ~/.lldbtest-config persiste…
6 # /Volumes/data/lldb/svn/trunk/test $ ./dotest.py -r /Volumes/data/lldb-test/archs -s session -c ..…
22 SB API. These are written in Python and use LLDB's ``dotest.py`` testing97 As mentioned before, ``dotest.py`` is LLDB's testing framework. The484 passing ``--param`` to lit and setting a value for ``dotest-args``.488 $ ./bin/llvm-lit -sv tools/lldb/test --param dotest-args='-C gcc'499 build you can use the ``lldb-dotest`` binary, which is a wrapper around500 ``dotest.py`` that passes all the arguments configured by CMake.509 $ ./bin/lldb-dotest -p TestInferiorCrashing.py522 $ ./bin/lldb-dotest functionalities/data-formatter532 $ python dotest.py -h617 #. Set test/dotest.py as the startup file[all …]
113 int dotest() in dotest() function174 dotest(); in main()
2 add_subdirectory(lldb-dotest)
8 define <1 x i64> @dotest(<1 x i64> %in0) {
15 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py settings28 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v settings220 test driver program dotest.py. For example, if we comment out the223 /Volumes/data/lldb/svn/trunk/test $ ./dotest.py -v settings
321 Convert the dotest style tests to use lldbutil.run_to_source_breakpoint