| /llvm-project/lldb/test/API/functionalities/gdb_remote_client/ |
| H A D | TestPlatformListProcesses.py | 40 processes = platform.GetAllProcesses(error) 42 self.assertEqual(processes.GetSize(), 2) 43 self.assertEqual(len(processes), 2) 46 processes.GetProcessInfoAtIndex(0, process_info) 50 processes.GetProcessInfoAtIndex(1, process_info)
|
| /llvm-project/lldb/test/API/functionalities/scripted_platform/ |
| H A D | my_scripted_platform.py | 9 self.processes = {} 18 self.processes[420] = proc 21 return self.processes 24 return self.processes[pid]
|
| /llvm-project/lldb/source/Plugins/Trace/intel-pt/ |
| H A D | TraceIntelPTBundleLoader.cpp | 209 if (bundle_description.processes) { in LoadBundle() 210 for (const JSONProcess &process : *bundle_description.processes) { in LoadBundle() 242 "processes?": [ in GetSchema() 309 - "cpus" is provided if and only if processes[].threads[].iptTrace is not provided. in GetSchema() 311 - If "kernel" is provided, then the "processes" section must be empty or not in GetSchema() 313 indicates that the kernel was traced and user processes weren't. Besides in GetSchema() 324 if (!bundle_description.cpus || !bundle_description.processes) in AugmentThreadsFromContextSwitches() 335 for (JSONProcess &process : *bundle_description.processes) { in AugmentThreadsFromContextSwitches() 374 std::vector<ProcessSP> processes; in CreateTraceIntelPTInstance() local 376 processes in CreateTraceIntelPTInstance() [all...] |
| H A D | TraceIntelPTJSONStructs.cpp | 137 {"processes", bundle_description.processes}, in toJSON() 149 if (!(o && o.map("processes", bundle_description.processes) && in fromJSON() 171 if (bundle_description.processes && in fromJSON() 172 !bundle_description.processes->empty()) { in fromJSON() 180 } else if (!bundle_description.processes) { in fromJSON()
|
| H A D | TraceIntelPTBundleSaver.cpp | 290 /// Build the processes section of the trace bundle description object. Besides 291 /// returning the processes information, this method saves to disk all modules 298 /// The directory where files will be saved when building the processes 302 /// The processes section or \a llvm::Error in case of failures. 324 std::vector<JSONProcess> processes; in BuildProcessesSection() 328 processes.push_back(std::move(*json_process)); in BuildProcessesSection() 332 return processes; in BuildProcessesSection() 338 std::vector<Process *> processes = trace_ipt.GetAllProcesses(); in BuildKernelSection() 339 Process *kernel_process = processes[0]; in BuildKernelSection() local 341 assert(processes in BuildKernelSection() 325 std::vector<JSONProcess> processes; BuildProcessesSection() local [all...] |
| /llvm-project/llvm/tools/opt-viewer/ |
| H A D | optpmap.py | 29 func, iterable, processes, should_print_progress, filter_=None, *args, **kwargs argument 46 if processes == 1: 55 processes=processes,
|
| /llvm-project/lldb/examples/python/templates/ |
| H A D | scripted_platform.py | 15 processes = None variable in ScriptedPlatform 26 processes = []
|
| /llvm-project/compiler-rt/test/profile/Posix/ |
| H A D | instrprof-gcov-parallel.test | 13 # Test if the .gcda file is correctly created from one of child processes 14 # and counters of all processes are recorded correctly.
|
| /llvm-project/llvm/docs/ |
| H A D | SecurityTransparencyReports.rst | 13 the purpose of the group and the processes it follows. Many of the group's 14 processes were still not well-defined enough for the group to operate well. 15 Over the course of 2021, the key processes were defined well enough to enable 39 the security group now has implemented all necessary processes for the group to 40 operate as promised. The group's processes can be improved further, and we do
|
| /llvm-project/bolt/test/X86/ |
| H A D | merge-fdata-bat-mode.test | 1 ## Check merge-fdata tool correctly processes fdata files with header strings
|
| H A D | indirect-goto.test | 1 ## Check llvm-bolt processes binaries compiled from sources that use indirect goto.
|
| H A D | dwarf4-override-comp-dir.test | 15 ;; Tests that BOLT processes .dwo files with --comp-dir-override.
|
| H A D | dwarf5-override-comp-dir.test | 15 ;; Tests that BOLT processes .dwo files with --comp-dir-override.
|
| H A D | phdr-out-of-order.test | 1 ## Check that llvm-bolt correctly processes a binary with program headers and
|
| /llvm-project/lldb/source/Target/ |
| H A D | Trace.cpp | 521 std::vector<Process *> processes; in GetTracedProcesses() local 525 processes.push_back(proc); in GetTracedProcesses() 528 processes.push_back(m_live_process); in GetTracedProcesses() 529 return processes; in GetTracedProcesses()
|
| /llvm-project/bolt/test/ |
| H A D | shared-object.test | 1 ## Test that llvm-bolt processes *.so without a failure
|
| /llvm-project/clang-tools-extra/docs/clang-tidy/checks/android/ |
| H A D | cloexec-pipe2.rst | 7 adds the O_CLOEXEC flag that marks the file descriptor to be closed in child processes.
|
| H A D | cloexec-pipe.rst | 8 be closed in child processes. Without this flag a sensitive file descriptor can be leaked to a
|
| /llvm-project/compiler-rt/test/asan/TestCases/Posix/ |
| H A D | log_path_fork_test.cc.disabled | 16 // There are two processes at this point, thus there should be two distinct
|
| /llvm-project/lldb/tools/debugserver/source/MacOSX/ |
| H A D | GenealogySPI.h | 91 typedef void (^os_diagnostic_block_t)(os_activity_process_list_t processes,
|
| H A D | Genealogy.cpp | 112 pid, 0, flags, ^(os_activity_process_list_t processes, int error) { in GetActivities() 114 m_os_activity_iterate_processes(processes, ^bool( in GetActivities()
|
| /llvm-project/lldb/test/API/functionalities/postmortem/elf-core/gcore/ |
| H A D | make-core.sh | 7 Your system prevents the use of PTRACE to attach to non-child processes. The core file
|
| /llvm-project/llvm/test/MC/ARM/ |
| H A D | arm-trustzone.s | 8 @ Check that the assembler processes SMC instructions when TrustZone support is
|
| H A D | arm-thumb-trustzone.s | 8 @ Check that the assembler processes SMC instructions when TrustZone support is
|
| /llvm-project/mlir/docs/Dialects/ |
| H A D | Mesh.md | 55 execution of a collective operation, all processes are in a coherent state. 63 the IR containing the `mesh` collectives, all processes would execute the same
|