[lldb] [doc] Sample commands prefix from > to $

[jankratochvil]

Summary

Remove all beginning > from the sample commands as my accidental copy-paste (multiple times...) will discard ./bin/llvm-lit which is difficult to rebuild (I have to rm -rf and cmake it all again).

lldb/docs/resources/test.rst

 
 It is possible to customize the architecture of the test binaries and compiler
 used by appending ``-A`` and ``-C`` options respectively to the CMake variable
 ``LLDB_TEST_USER_ARGS``. For example, to test LLDB against 32-bit binaries
 built with a custom version of clang, do:
 
 ::
 
-   > cmake -DLLDB_TEST_USER_ARGS="-A i386 -C /path/to/custom/clang" -G Ninja
-   > ninja check-lldb
+   $ cmake -DLLDB_TEST_USER_ARGS="-A i386 -C /path/to/custom/clang" -G Ninja
+   $ ninja check-lldb
 
 Note that multiple ``-A`` and ``-C`` flags can be specified to
 ``LLDB_TEST_USER_ARGS``.
 
 Running a Single Test Suite
 ---------------------------
 
 Each test suite can be run separately, similar to running the whole test suite

 ---------------------
 
 The recommended way to run a single test is by invoking the lit driver with a
 filter. This ensures that the test is run with the same configuration as when
 run as part of a test suite.
 
 ::
 
-   > ./bin/llvm-lit -sv tools/lldb/test --filter <test>
+   $ ./bin/llvm-lit -sv tools/lldb/test --filter <test>
 
 
 Because lit automatically scans a directory for tests, it's also possible to
 pass a subdirectory to run a specific subset of the tests.
 
 ::
 
-   > ./bin/llvm-lit -sv tools/lldb/test/Shell/Commands/CommandScriptImmediateOutput
+   $ ./bin/llvm-lit -sv tools/lldb/test/Shell/Commands/CommandScriptImmediateOutput
 
 
 For the SB API tests it is possible to forward arguments to ``dotest.py`` by
 passing ``--param`` to lit and setting a value for ``dotest-args``.
 
 ::
 
-   > ./bin/llvm-lit -sv tools/lldb/test --param dotest-args='-C gcc'
+   $ ./bin/llvm-lit -sv tools/lldb/test --param dotest-args='-C gcc'
 
 
 Below is an overview of running individual test in the unit and API test suites
 without going through the lit driver.
 
 Running a Specific Test or Set of Tests: API Tests
 --------------------------------------------------
 
 In addition to running all the LLDB test suites with the ``check-lldb`` CMake
 target above, it is possible to run individual LLDB tests. If you have a CMake
 build you can use the ``lldb-dotest`` binary, which is a wrapper around
 ``dotest.py`` that passes all the arguments configured by CMake.
 
 Alternatively, you can use ``dotest.py`` directly, if you want to run a test
 one-off with a different configuration.
 
 For example, to run the test cases defined in TestInferiorCrashing.py, run:
 
 ::
 
-   > ./bin/lldb-dotest -p TestInferiorCrashing.py
+   $ ./bin/lldb-dotest -p TestInferiorCrashing.py
 
 ::
 
-   > cd $lldb/test
-   > python dotest.py --executable <path-to-lldb> -p TestInferiorCrashing.py ../packages/Python/lldbsuite/test
+   $ cd $lldb/test
+   $ python dotest.py --executable <path-to-lldb> -p TestInferiorCrashing.py ../packages/Python/lldbsuite/test
 
 If the test is not specified by name (e.g. if you leave the ``-p`` argument
 off),  all tests in that directory will be executed:
 
 
 ::
 
-   > ./bin/lldb-dotest functionalities/data-formatter
+   $ ./bin/lldb-dotest functionalities/data-formatter
 
 ::
 
-   > python dotest.py --executable <path-to-lldb> functionalities/data-formatter
+   $ python dotest.py --executable <path-to-lldb> functionalities/data-formatter
 
 Many more options that are available. To see a list of all of them, run:
 
 ::
 
-   > python dotest.py -h
+   $ python dotest.py -h
 
 
 Running a Specific Test or Set of Tests: Unit Tests
 ---------------------------------------------------
 
 The unit tests are simple executables, located in the build directory under ``tools/lldb/unittests``.
 
 To run them, just run the test binary, for example, to run all the Host tests:
 
 ::
 
-   > ./tools/lldb/unittests/Host/HostTests
+   $ ./tools/lldb/unittests/Host/HostTests
 
 
 To run a specific test, pass a filter, for example:
 
 ::
 
-   > ./tools/lldb/unittests/Host/HostTests --gtest_filter=SocketTest.DomainListenConnectAccept
+   $ ./tools/lldb/unittests/Host/HostTests --gtest_filter=SocketTest.DomainListenConnectAccept
 
 
 Running the Test Suite Remotely
 -------------------------------
 
 Running the test-suite remotely is similar to the process of running a local
 test suite, but there are two things to have in mind: