| /llvm-project/lldb/docs/use/ |
| H A D | map.rst | 24 .. code-block:: shell
29 .. code-block:: shell
38 .. code-block:: shell
44 .. code-block:: shell
53 .. code-block:: shell
61 .. code-block:: shell
73 .. code-block:: shell
81 .. code-block:: shell
92 .. code-block:: shell
100 .. code-block:: shell
[all...] |
| H A D | symbols.rst | 15 - Running one or more shell scripts
21 or modified using the **defaults** shell command:
50 strings. Specifies a shell script that will get run in order to find the
51 dSYM. The shell script will be run given a single UUID value as the
52 shell command arguments and the shell command is expected to return a
76 Shell Script Property List Format
79 Shell scripts that are specified with the **DBGShellCommands** defaults key
81 The shell script will be invoked with a single UUID string value like
82 "23516BE4-29BE-350C-91C9-F36E7999F0F1". The shell script must respond with a
132 Below is a sample shell script output for a binary that contains two
[all …]
|
| /llvm-project/lldb/test/API/commands/platform/basic/ |
| H A D | TestPlatformCommand.py | 22 "help shell",
24 "Run a shell command on the host.",
25 "shell <shell-command>",
26 "'shell' is an abbreviation",
29 # "platform shell" has options. The "shell" alias for it does not.
30 self.expect("help shell", substrs=["Command Options:"], matching=False)
65 """Test that the platform shell command can invoke ls."""
68 self.expect("platform shell dir c:\\", substrs=["Windows", "Program Files"])
69 self.expect("shell dir c:\\", substrs=["Windows", "Program Files"])
71 self.expect("platform shell ls /", substrs=["cache", "dev", "system"])
[all …]
|
| /llvm-project/llvm/utils/lit/tests/ |
| H A D | shtest-shell.py | 1 # Check the internal shell handling component of the ShTest format.
3 # RUN: not %{lit} -v %{inputs}/shtest-shell > %t.out
9 # Test again in non-UTF shell to catch potential errors with python 2 seen
11 # RUN: env PYTHONIOENCODING=ascii not %{lit} -a %{inputs}/shtest-shell > %t.ascii.out
21 # CHECK: FAIL: shtest-shell :: colon-error.txt
22 # CHECK: *** TEST 'shtest-shell :: colon-error.txt' FAILED ***
29 # CHECK: PASS: shtest-shell :: continuations.txt
31 # CHECK: PASS: shtest-shell :: dev-null.txt
33 # CHECK: FAIL: shtest-shell :: diff-b.txt
34 # CHECK: *** TEST 'shtest-shell
[all...] |
| H A D | shtest-run-at-line.py | 13 # In the case of the external shell, we check for only RUN lines in stderr in
14 # case some shell implementations format "set -x" output differently.
16 # CHECK-LABEL: FAIL: shtest-run-at-line :: external-shell/basic.txt
27 # CHECK-LABEL: FAIL: shtest-run-at-line :: external-shell/empty-run-line.txt
37 # CHECK-LABEL: FAIL: shtest-run-at-line :: external-shell/line-continuation.txt
39 # The execution trace from an external sh-like shell might print the commands
51 # CHECK-LABEL: FAIL: shtest-run-at-line :: external-shell/run-line-with-newline.txt
61 # CHECK-LABEL: FAIL: shtest-run-at-line :: internal-shell/basic.txt
73 # CHECK-LABEL: FAIL: shtest-run-at-line :: internal-shell/empty-run-line.txt
83 # CHECK-LABEL: FAIL: shtest-run-at-line :: internal-shell/line-continuation.txt
[all …]
|
| H A D | shtest-timeout.py | 10 # Test per test timeout using external shell
17 # CHECK-EXTSH-ERR: Using external shell
19 # Test per test timeout using internal shell
30 # CHECK-INTSH-ERR: Using internal shell
40 # CHECK-CFGSET-ERR: Using internal shell
54 # Test per test timeout using external shell
61 # Test per test timeout using internal shell
|
| H A D | shtest-external-shell-kill.py | 1 # This test exercises an external shell use case that, at least at one time,
18 # manage to terminate the shell running lit.
23 # RUN: %{lit} -a %{inputs}/shtest-external-shell-kill | %{filter-lit} | FileCheck %s
|
| /llvm-project/lldb/test/Shell/ |
| H A D | CMakeLists.txt | 1 add_custom_target(lldb-shell-test-deps)
2 set_target_properties(lldb-shell-test-deps PROPERTIES FOLDER "LLDB/Tests")
3 add_dependencies(lldb-shell-test-deps lldb-test-depends)
5 add_lit_testsuites(LLDB-SHELL
7 DEPENDS lldb-shell-test-deps)
21 add_lit_testsuite(check-lldb-shell "Running lldb shell test suite"
24 DEPENDS lldb-shell-test-deps)
|
| H A D | lit.site.cfg.py.in | 35 # The shell tests use their own module caches.
36 config.lldb_module_cache = os.path.join("@LLDB_TEST_MODULE_CACHE_LLDB@", "lldb-shell")
37 config.clang_module_cache = os.path.join("@LLDB_TEST_MODULE_CACHE_CLANG@", "lldb-shell")
43 lit_config.load_config(config, os.path.join(config.lldb_src_root, "test", "Shell", "lit.cfg.py"))
|
| /llvm-project/clang/tools/clang-format-vs/ClangFormat/ |
| H A D | ClangFormat.csproj | |
| H A D | packages.config | |
| /llvm-project/libcxx/utils/ |
| H A D | adb_run.py | 69 run_adb_sync_command(["adb", "shell", "mkdir", "-p", remote_dir])
102 # - Replacing older shell utilities with toybox (e.g. on old devices).
112 # If we're running as root, switch to the shell user. The libc++
116 # run as the shell user.
119 # which might be owned by root. Before switching to shell, make the
125 # - Starting in Android M, su from root->shell resets PATH, so we need
136 " su shell \"$(command -v env)\" PATH=\"$PATH\" \"$@\";"
138 " su shell \"$@\";"
151 # Prior to the adb feature "shell_v2" (added in Android N), `adb shell`
155 # - The exit code of the shell comman
[all...] |
| /llvm-project/compiler-rt/lib/asan/scripts/ |
| H A D | asan_device_setup | 41 $ADB shell su -c "rm \\\"$2/$FILENAME\\\"" >&/dev/null
42 $ADB shell su -c "cat \\\"/data/local/tmp/$FILENAME\\\" > \\\"$2/$FILENAME\\\""
43 $ADB shell su -c "rm \\\"/data/local/tmp/$FILENAME\\\""
51 local STORAGE=`$ADB shell mount | grep /system | cut -d ' ' -f1`
54 $ADB shell su -c "mount -o rw,remount $STORAGE /system"
63 $ADB shell $@
65 $ADB shell su -c "$*"
84 $ADB shell rm "/data/local/tmp/$FILENAME" >&/dev/null
85 …$ADB shell su -c "[ -f \\\"$1\\\" ] && cat \\\"$1\\\" > \\\"/data/local/tmp/$FILENAME\\\" && chown…
86 …$ADB pull "/data/local/tmp/$FILENAME" "$2" >&/dev/null && $ADB shell "rm \"/data/local/tmp/$FILENA…
[all …]
|
| /llvm-project/llvm/utils/ |
| H A D | bisect-skip-count | 41 # Use shell support if you need to use complex shell expressions in your command
42 parser.add_argument('--shell', type=bool, default=False)
61 result = subprocess.call(cmd, shell=args.shell, timeout=args.timeout)
84 result = subprocess.call(cmd, shell=args.shell, timeout=args.timeout)
|
| H A D | update_test_body.py | 67 if args.shell:
68 print(f"invoke shell in the temporary directory '{dir}'")
69 subprocess.run([os.environ.get("SHELL", "sh")])
104 "--shell", action="store_true", help="invoke shell instead of 'gen'"
|
| /llvm-project/libc/benchmarks/ |
| H A D | README.md | 13 ```shell
20 ```shell
40 ```shell
68 ```shell
82 ```shell
90 ```shell
|
| /llvm-project/lldb/include/lldb/Host/ |
| H A D | Host.h | 197 /// Run a shell command.
212 /// Run a shell command.
213 /// \arg shell Pass an empty string if you want to use the default shell
221 static Status RunShellCommand(llvm::StringRef shell, llvm::StringRef command,
228 /// Run a shell command.
242 /// Run a shell command.
243 /// \arg shell Pass an empty string if you want to use the default
244 /// shell interpreter \arg command \arg working_dir Pass empty FileSpec to use
251 static Status RunShellCommand(llvm::StringRef shell, cons
[all...] |
| /llvm-project/llvm/utils/TableGen/jupyter/ |
| H A D | README.md | 26 ```shell
35 ```shell
52 ```shell
64 ```shell
|
| /llvm-project/lldb/test/API/macosx/lc-note/firmware-corefile/ |
| H A D | TestFirmwareCorefiles.py | 40 shell=True,
48 shell=True,
58 shell=True,
144 shell=True,
154 shell=True,
164 shell=True,
254 shell=True,
257 ## We can hook in our dsym-for-uuid shell script to lldb with this env
290 ('/usr/bin/dwarfdump --uuid "%s"' % aout_exe), shell=True
299 ### Create our dsym-for-uuid shell script which returns aout_exe
|
| /llvm-project/libc/benchmarks/automemcpy/ |
| H A D | README.md | |
| /llvm-project/lldb/test/Shell/Host/ |
| H A D | TestCustomShell.test | 9 # RUN: SHELL=bogus not %lldb %t.out -b -o 'process launch -X 1 --' 2>&1 | FileCheck %s --check-pref…
12 # ERROR: error: shell expansion failed
13 # CHECK-NOT: error: shell expansion failed
|
| /llvm-project/clang/utils/analyzer/ |
| H A D | SATest.py | 156 elif args.shell:
163 sys.exit(call("docker build --tag satest-image {}".format(SCRIPTS_DIR), shell=True))
170 # while the shell session is in progress.
173 call("docker exec -it satest bash", shell=True)
201 shell=True,
210 call("docker stop satest", shell=True)
397 "--shell", action="store_true", help="Start a shell on docker."
|
| /llvm-project/lldb/docs/resources/ |
| H A D | test.rst | 10 * **Shell tests**: Integration tests that test the debugger through the command
39 Shell Tests
42 Shell tests are located under ``lldb/test/Shell``. These tests are generally
44 ``lldb-test`` using ``FileCheck``. Shell tests are generally small and fast to
53 Obviously shell tests are great for testing the command line driver itself or
60 A good rule of thumb is to prefer shell tests when what is being tested is
63 match with ``FileCheck``. Though Shell tests can be run remotely, behavior
67 inferiors. For shell tests, they have to be relatively simple. The
69 and different variants, which is described in more detail below, while shell
[all...] |
| /llvm-project/lldb/test/API/python_api/target-arch-from-module/ |
| H A D | TestTargetArchFromModule.py | 30 # We can hook in our dsym-for-uuid shell script to lldb with
39 ('/usr/bin/dwarfdump --uuid "%s"' % aout_exe), shell=True
48 ### Create our dsym-for-uuid shell script which returns self.hidden_aout_exe.
95 # the LLDB_APPLE_DSYMFORUUID_EXECUTABLE shell script -
|
| /llvm-project/lldb/test/API/macosx/lc-note/kern-ver-str/ |
| H A D | TestKernVerStrLCNOTE.py | 28 ## We can hook in our dsym-for-uuid shell script to lldb with this env
37 ('/usr/bin/dwarfdump --uuid "%s"' % self.test_exe), shell=True
46 ### Create our dsym-for-uuid shell script which returns self.test_exe
85 self.create_corefile + " " + self.corefile + " " + self.test_exe, shell=True
|