jhpratt / num_threads Goto Github PK

cargo run --target aarch64-apple-darwin               
   Compiling test-threadcount v1.0.0 (...)
    Finished dev [unoptimized + debuginfo] target(s) in 0.51s
     Running `target/aarch64-apple-darwin/debug/test-threadcount`

cargo run --target x86_64-apple-darwin                
   Compiling test-threadcount v1.0.0 (...)
    Finished dev [unoptimized + debuginfo] target(s) in 0.19s
     Running `target/x86_64-apple-darwin/debug/test-threadcount`
thread 'main' panicked at src/main.rs:2:5:
assertion `left == right` failed
  left: Some(2)
 right: Some(1)
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

lldb target/x86_64-apple-darwin/debug/test-threadcount
(lldb) target create "target/x86_64-apple-darwin/debug/test-threadcount"
Current executable set to '.../target/x86_64-apple-darwin/debug/test-threadcount' (x86_64).
(lldb) break set --file src/main.rs --line 3
Breakpoint 1: where = test-threadcount`test_threadcount::main::h0b4a5b9d24100f68 + 11 at main.rs:3:9, address = 0x00000001000019ab
(lldb) run
Process 48950 launched: '.../target/x86_64-apple-darwin/debug/test-threadcount' (x86_64)
warning: libobjc.A.dylib is being read from process memory. This indicates that LLDB could not read from the host's in-memory shared cache. This will likely reduce debugging performance.

Process 48950 stopped
* thread #1, name = 'main', queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
    frame #0: 0x00000001000019ab test-threadcount`test_threadcount::main::h0b4a5b9d24100f68 at main.rs:3:9
   1    fn main() {
   2        assert_eq!(
-> 3            num_threads::num_threads(),
   4            std::num::NonZeroUsize::new(1)
   5        )
   6    }
Target 0: (test-threadcount) stopped.
(lldb) thread list
Process 48950 stopped
* thread #1: tid = 0x2dfb06, 0x00000001000019ab test-threadcount`test_threadcount::main::h0b4a5b9d24100f68 at main.rs:3:9, name = 'main', queue = 'com.apple.main-thread', stop reason = breakpoint 1.1
(lldb) ^D

   In addition, CLONE_THREAD, CLONE_SIGHAND, and CLONE_VM can be
   specified in flags if the caller is single threaded (i.e., it is
   not sharing its address space with another process or thread).
   In this case, these flags have no effect.  (Note also that
   specifying CLONE_THREAD automatically implies CLONE_VM, and
   specifying CLONE_VM automatically implies CLONE_SIGHAND.)  If the
   process is multithreaded, then the use of these flags results in
   an error.

running 2 tests
test test::is_single_threaded ... FAILED
test test::num_threads ... FAILED

failures:

---- test::is_single_threaded stdout ----
thread 'test::is_single_threaded' panicked at 'assertion failed: `(left == right)`
  left: `Some(false)`,
 right: `Some(true)`', src/lib.rs:56:13

---- test::num_threads stdout ----
thread 'test::num_threads' panicked at 'assertion failed: `(left == right)`
  left: `Some(3)`,
 right: `Some(1)`', src/lib.rs:44:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    test::is_single_threaded
    test::num_threads

     Running `/builddir/build/BUILD/num_threads-0.1.6/target/release/deps/num_threads-03ca46149c224543 --test-threads 1`
running 2 tests
test test::is_single_threaded ... FAILED
test test::num_threads ... FAILED
failures:
---- test::is_single_threaded stdout ----
thread 'test::is_single_threaded' panicked at 'assertion failed: `(left == right)`
  left: `Some(false)`,
 right: `Some(true)`', src/lib.rs:56:13
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
---- test::num_threads stdout ----
thread 'test::num_threads' panicked at 'assertion failed: `(left == right)`
  left: `Some(2)`,
 right: `Some(1)`', src/lib.rs:44:13
failures:
    test::is_single_threaded
    test::num_threads
test result: FAILED. 0 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
error: test failed, to rerun pass `--lib`

          (20) num_threads  %ld
                 Number of threads in this process (since Linux
                 2.6).  Before kernel 2.6, this field was hard coded
                 to 0 as a placeholder for an earlier removed field.

$ cat /proc/self/stat
18477 (cat) R 16603 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 21552080 0 0 0 0 0 70368752569616 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
$ cat /proc/self/status | grep Thread
Threads:	2
$ ls /proc/self/task
18505  18507
$