/openbsd-src/gnu/usr.bin/perl/dist/threads/t/ |
H A D | state.t | 108 ok($thr->is_running(), 'thread running'); 109 ok(threads->list(threads::running) == 1, 'thread running list'); 116 ok(! $thr->is_running(), 'thread not running'); 117 ok(threads->list(threads::running) == 0, 'thread running list'); 124 ok(! $thr->is_running(), 'thread not running'); 125 ok(threads->list(threads::running) == 0, 'thread running list'); 133 ok($thr->is_running(), 'thread running'); 134 ok(threads->list(threads::running) == 0, 'thread running list'); 141 ok(! $thr->is_running(), 'thread not running'); 142 ok(threads->list(threads::running) == 0, 'thread running list'); [all …]
|
/openbsd-src/gnu/usr.bin/cvs/ |
H A D | INSTALL | 106 DEC Alpha running OSF/1 version 1.3 using cc (about 1.4A2) 107 DEC Alpha running OSF/1 version 2.0 (1.8) 108 DEC Alpha running OSF/1 version 2.1 (about 1.4A2) 109 DEC Alpha running OSF/1 version 3.0 (1.5.95) (footnote 7) 110 DEC Alpha running OSF/1 version 3.2 (1.9) 111 Alpha running alpha-dec-osf4.0 (1.10) 112 DEC Alpha running Digital UNIX v4.0C using gcc 2.7.2.2 (1.9.14) 113 DEC Alpha running VMS 6.2 (1.8.85 client-only) 114 Alpha running NetBSD 1.2E (1.10) 119 HP 9000/710 running HP-UX 8.07A using gcc (about 1.4A2) [all …]
|
/openbsd-src/gnu/llvm/llvm/docs/ |
H A D | OptBisect.rst | 119 BISECT: running pass (1) Simplify the CFG on function (g) 120 BISECT: running pass (2) SROA on function (g) 121 BISECT: running pass (3) Early CSE on function (g) 122 BISECT: running pass (4) Infer set function attributes on module (test.ll) 123 …BISECT: running pass (5) Interprocedural Sparse Conditional Constant Propagation on module (test.l… 124 BISECT: running pass (6) Global Variable Optimizer on module (test.ll) 125 BISECT: running pass (7) Promote Memory to Register on function (g) 126 BISECT: running pass (8) Dead Argument Elimination on module (test.ll) 127 BISECT: running pass (9) Combine redundant instructions on function (g) 128 BISECT: running pass (10) Simplify the CFG on function (g) [all …]
|
/openbsd-src/sys/dev/pci/drm/i915/gvt/ |
H A D | execlist.c | 66 gvt_dbg_el("[before] running slot %d/context %x pending slot %d\n", in switch_virtual_execlist_slot() 79 gvt_dbg_el("[after] running slot %d/context %x pending slot %d\n", in switch_virtual_execlist_slot() 90 struct intel_vgpu_execlist_slot *running = execlist->running_slot; in emulate_execlist_status() local 101 if (running) { in emulate_execlist_status() 102 status.current_execlist_pointer = !!running->index; in emulate_execlist_status() 103 status.execlist_write_pointer = !!!running->index; in emulate_execlist_status() 105 !!!(running->index); in emulate_execlist_status() 107 !!(running->index); in emulate_execlist_status() 185 struct intel_vgpu_execlist_slot *running = execlist->running_slot; in emulate_execlist_ctx_schedule_out() local 187 struct execlist_ctx_descriptor_format *ctx0 = &running->ctx[0]; in emulate_execlist_ctx_schedule_out() [all …]
|
/openbsd-src/gnu/usr.bin/binutils/gdb/testsuite/gdb.base/ |
H A D | so-indr-cl.exp | 96 # whether a user can set breakpoints in a shlib before running the 111 -re "Cannot break on solib_main without a running program.*$gdb_prompt $"\ 112 {pass "break on indirect solib call before running"} 114 {pass "break on indirect solib call before running 2"} 116 {fail "break on indirect solib call before running"} 117 timeout {fail "(timeout) break on indirect solib call before running"} 122 # once the inferior is running, gdb consults the debug info rather than 132 {pass "break on indirect solib call after running"} 134 {fail "break on indirect solib call after running"} 135 timeout {fail "(timeout) break on indirect solib call after running"}
|
H A D | chng-syms.exp | 61 fail "running to stop_here $ident" 65 fail "running to stop_here $ident (timeout)" 98 # (vacuously) passed providing that re-running it succeeds as before. 109 pass "running with invalidated bpt condition after executable changes" 112 pass "running with invalidated bpt condition after executable changes" 115 fail "running with invalidated bpt condition after executable changes" 118 fail "(timeout) running with invalidated bpt condition after executable changes"
|
H A D | page.exp | 47 "running -- Running the program" 74 "running -- Running the program"
|
/openbsd-src/regress/sys/net/pflow/ |
H A D | ifconfig.ok | 15 pflow0: flags=41<UP,RUNNING> mtu 1492 19 pflow0: flags=41<UP,RUNNING> mtu 1492 31 pflow0: flags=41<UP,RUNNING> mtu 1492 36 pflow0: flags=41<UP,RUNNING> mtu 1492 40 pflow0: flags=41<UP,RUNNING> mtu 1448 44 pflow0: flags=41<UP,RUNNING> mtu 1492 49 pflow0: flags=41<UP,RUNNING> mtu 1492
|
/openbsd-src/usr.sbin/ldomctl/ |
H A D | ldomctl.8 | 33 information about domains running on the system. 82 Indicate the currently running configuration, 84 (after resetting the machine) if it differs from the currently running one. 89 The exact behaviour of this command depends on the OS running in the domain. 110 or for all domains running on the system. 181 primary - running OpenBSD running 1% 182 puffy ttyV0 running OpenBoot Primary Boot Loader 8% 183 salmah ttyV1 running OpenBoot Primary Boot Loader 12%
|
/openbsd-src/gnu/usr.bin/perl/t/lib/warnings/ |
H A D | taint | 3 Insecure %s%s while running with -T switch 24 Insecure dependency in chdir while running with -T switch at - line 12. 49 Insecure dependency in chdir while running with -T switch at - line 12. 50 Insecure dependency in chdir while running with -T switch at - line 17. 77 Insecure dependency in chdir while running with -t switch at - line 12. 78 Insecure dependency in chdir while running with -t switch at - line 17.
|
/openbsd-src/share/man/man8/ |
H A D | rc.subr.8 | 159 Return 0 if the daemon is running or 1 if it is not. 161 Check that the service is running by calling 163 If it's not running, call 168 Check that the service is running by calling 170 If it is running, 185 Check that the service is running by calling 187 If it is running, 192 Check daemon configuration before running 282 Change to this directory before running
|
/openbsd-src/gnu/llvm/lldb/docs/resources/ |
H A D | test.rst | 190 generic tests, so running the test suite with the feature enabled is a good way 199 feature. This can often be done by running the test suite with different 219 Launching a process and running to a breakpoint can often be the most 231 possible to test `SBValue` by running expressions with 234 Functionality that always requires a running process is everything that 238 environment also always require a running process. 256 ``@no_debug_info_test`` (which will avoid running all debug information 280 test executable and running the process to a breakpoint). Using these 301 When running the same command in LLDB the reason for the unexpected success 387 This tells the test harness that unless we are running "linux" and clang version equal & above 8.0,… [all …]
|
/openbsd-src/usr.bin/make/ |
H A D | job.h | 45 * Definitions pertaining to the running of jobs. 49 * register a new job running commands associated with building gn. 76 * wait until something happens, like a job finishing running a command 81 * handle running jobs until they're finished. 88 * By displaying STATUS info, or by aborting running jobs for a fatal 100 extern bool sequential; /* True if we are running one single-job */
|
/openbsd-src/gnu/usr.bin/binutils/gdb/gdbserver/ |
H A D | gdbserver.1 | 21 than the one which is running the program being debugged. 28 the GDB running on the host system. 58 On some targets, gdbserver can also attach to running programs. 63 PID is the process ID of a currently running process. It isn't 64 necessary to point gdbserver at a binary for the running process. 71 --baud option if the serial line is running at anything except 9600 baud.)
|
H A D | README | 17 the GDB running on the host system. 47 On some targets, gdbserver can also attach to running programs. This is 52 PID is the process ID of a currently running process. It isn't necessary 53 to point gdbserver at a binary for the running process. 60 --baud option if the serial line is running at anything except 9600 baud.) 123 should connect to (typically the same as the host running gdb):
|
/openbsd-src/gnu/usr.bin/binutils/gdb/ |
H A D | NEWS | 179 Sun 3, running SunOS 3 m68*-*-sunos3* 180 Sun 3, running SunOS 4 m68*-*-sunos4* 181 Sun 2, running SunOS 3 m68000-*-sunos3* 182 Sun 2, running SunOS 4 m68000-*-sunos4* 183 Motorola 680x0 running LynxOS m68*-*-lynxos* 197 command line option "-i=tui" or by running the separate "gdbtui" 319 Sun 3, running SunOS 3 m68*-*-sunos3* 320 Sun 3, running SunOS 4 m68*-*-sunos4* 321 Sun 2, running SunOS 3 m68000-*-sunos3* 322 Sun 2, running SunOS 4 m68000-*-sunos4* [all …]
|
/openbsd-src/gnu/llvm/libcxx/utils/ci/ |
H A D | run-buildbot-container | 3 # This script starts a shell in a container running the libc++ build bot Docker 13 # is useful for editing files on the host machine and re-running the build bot 18 # If you need to do this, give that user permission to do so after running 26 … echo "Was unable to find the root of the LLVM monorepo; are you running from within the monorepo?"
|
H A D | run-buildbot | 33 running back-deployment testing if one wants to override 44 when running the 'format' builder. 129 # when building tests) to allow enabling filesystem for running tests, 144 echo "+++ Running the libc++ tests" 147 echo "+++ Running the libc++abi tests" 150 echo "+++ Running the libunwind tests" 157 echo "+++ Running the libc++ ABI list test" 166 echo "--- Running the benchmarks" 332 echo "+++ Running the libc++ and libc++abi tests" 586 # TODO: Currently, building with the experimental library breaks running [all …]
|
/openbsd-src/gnu/llvm/libcxx/docs/ |
H A D | TestingLibcxx.rst | 28 running ``llvm-lit`` on a specified test or directory. If you're unsure 49 target before running the tests manually with ``lit`` when you make any sort of 52 Sometimes you'll want to change the way LIT is running the tests. Custom options 69 like the compiler to use for running the tests, which default compiler and linker 81 ``llvm/utils/lit/lit.py``) to that file. So when you're running 109 building the tests on one host but running them on a different host, which add a 166 Running Benchmarks 180 For more information about running benchmarks see `Google Benchmark`_.
|
/openbsd-src/games/worm/ |
H A D | worm.c | 61 int running = 0; variable 155 if (running) { in main() 156 running--; in main() 300 running = RUNLEN; in process() 305 running = RUNLEN/2; in process() 310 running = RUNLEN/2; in process() 315 running = RUNLEN; in process() 353 running = 0; in process() 368 if (!(slow && running)) { in process()
|
/openbsd-src/usr.bin/dig/lib/isc/unix/ |
H A D | app.c | 50 int running; member 76 ctx->running = 0; in isc_app_ctxstart() 111 if (ctx->running) { in isc_app_ctxonrun() 207 if (!ctx->running) { in isc_app_ctxrun() 208 ctx->running = 1; in isc_app_ctxrun() 239 REQUIRE(ctx->running); in isc_app_ctxshutdown()
|
/openbsd-src/share/snmp/ |
H A D | HOST-RESOURCES-MIB.txt | 236 running on this system." 504 running(2), 516 unknown. running(2) indicates that the device is up 517 and running and that no unusual error conditions are 1068 -- The Host Resources Running Software Group 1071 -- software that is running or loaded into physical or virtual 1072 -- memory in preparation for running. This includes the host's 1081 that represents the primary operating system running 1091 "The (conceptual) table of software running on the 1101 running on the host Note that because the installed [all …]
|
/openbsd-src/gnu/usr.bin/perl/Cross/ |
H A D | build-arm-n770-sh | 71 echo "running $cmd" 74 echo "running $cmd" 81 echo "running $cmd" 85 echo "running $cmd"
|
/openbsd-src/gnu/llvm/compiler-rt/include/xray/ |
H A D | xray_records.h | 78 // The CPU where the thread is running. We assume number of CPUs <= 256. 94 // The thread ID for the currently running thread. 97 // The ID of process that is currently running 117 // The thread ID for the currently running thread. 120 // The ID of process that is currently running
|
/openbsd-src/gnu/usr.bin/perl/cpan/Test-Harness/lib/TAP/Harness/ |
H A D | Beyond.pod | 7 Test::Harness is responsible for running test scripts, analysing 39 running my tests against the installed version rather than the new 124 running multiple test scripts in parallel. This is particularly 134 or attempt to listen on the same socket I'll have problems running 162 exit before running all the expected tests. The following lines are 289 (TAP::Parser::Scheduler) to work out the running order for the 294 If I'm running my tests in parallel there may also be a multiplexer 298 Once it has created those helpers TAP::Harness starts running the 300 is responsible for running the test script and parsing its output. 324 and tokenise their output. Before running a test script TAP::Parser [all …]
|