-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: the main thread terminated without waiting for all remaining threads
note: pass `-Zmiri-ignore-leaks` to disable this check
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: trying to join a detached or already joined thread
--> $DIR/libc_pthread_join_detached.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: trying to join a detached or already joined thread
--> $DIR/libc_pthread_join_joined.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: trying to join a detached or already joined thread
--> $DIR/libc_pthread_join_main.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: trying to join a detached or already joined thread
--> $DIR/libc_pthread_join_multiple.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: trying to join itself
--> $DIR/libc_pthread_join_self.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: pointer to ALLOC was dereferenced after this allocation got freed
--> $DIR/thread_local_static_dealloc.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: callee has fewer arguments than expected
--> $DIR/too_few_args.rs:LL:CC
|
= note: inside `thread_start` at RUSTLIB/std/src/panic.rs:LL:CC
= note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: callee has more arguments than expected
--> $DIR/too_many_args.rs:LL:CC
|
= note: inside `thread_start` at RUSTLIB/std/src/panic.rs:LL:CC
= note: this error originates in the macro `$crate::panic::panic_2015` (in Nightly builds, run with -Z macro-backtrace for more info)
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
thread '<unnamed>' panicked at 'explicit panic', $DIR/unwind_top_of_stack.rs:LL:CC
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: Undefined Behavior: unwinding past the topmost frame of the stack
= note: inside `thread_start` at $DIR/unwind_top_of_stack.rs:LL:CC
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 2) and Allocate on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/alloc_read_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 2) and Allocate on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/alloc_write_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Atomic Load on Thread(id = 2) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/atomic_read_na_write_race1.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 2) and Atomic Load on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/atomic_read_na_write_race2.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 2) and Atomic Store on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/atomic_write_na_read_race1.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Atomic Store on Thread(id = 2) and Read on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/atomic_write_na_read_race2.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Atomic Store on Thread(id = 2) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/atomic_write_na_write_race1.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 2) and Atomic Store on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/atomic_write_na_write_race2.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 3) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/dangling_thread_async_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 0, name = "main") and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/dangling_thread_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Deallocate on Thread(id = 2) and Read on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/dealloc_read_race1.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: pointer to ALLOC was dereferenced after this allocation got freed
--> $DIR/dealloc_read_race2.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Deallocate on Thread(id = 1) and Read on Thread(id = 2) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/dealloc_read_race_stack.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Deallocate on Thread(id = 2) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/dealloc_write_race1.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: pointer to ALLOC was dereferenced after this allocation got freed
--> $DIR/dealloc_write_race2.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Deallocate on Thread(id = 1) and Write on Thread(id = 2) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/dealloc_write_race_stack.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 6) and Write on Thread(id = 5) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/enable_after_join_to_main.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 0, name = "main") and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/fence_after_load.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 2) and Read on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/read_write_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 1) and Write on Thread(id = 2) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/read_write_race_stack.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 3) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/relax_acquire_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 3) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/release_seq_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 2) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/release_seq_race_same_thread.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Read on Thread(id = 3) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/rmw_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 2) and Write on Thread(id = 1) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/write_write_race.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: Data race detected between Write on Thread(id = 1) and Write on Thread(id = 2) at ALLOC (current vector clock = VClock, conflicting timestamp = VClock)
--> $DIR/write_write_race_stack.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
// ignore-windows: Concurrency on Windows is not supported yet.
// compile-flags: -Zmiri-ignore-leaks
-// error-pattern:
+// error-pattern: unreachable
// https://plv.mpi-sws.org/scfix/paper.pdf
// 2.2 Second Problem: SC Fences are Too Weak
// Our ui_test does not yet support overriding failure status codes.
if (b, c) == (0, 0) {
// This *should* be unreachable, but Miri will reach it.
- std::process::exit(1);
+ unsafe { std::hint::unreachable_unchecked(); }
}
}
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
+error: Undefined Behavior: entering unreachable code
+ --> RUSTLIB/core/src/hint.rs:LL:CC
+ |
+LL | unsafe { intrinsics::unreachable() }
+ | ^^^^^^^^^^^^^^^^^^^^^^^^^ entering unreachable code
+ |
+ = help: this indicates a bug in the program: it performed an invalid operation, and caused Undefined Behavior
+ = help: see https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html for further information
+
+ = note: inside `std::hint::unreachable_unchecked` at RUSTLIB/core/src/hint.rs:LL:CC
+note: inside `test_cpp20_rwc_syncs` at $DIR/cpp20_rwc_syncs.rs:LL:CC
+ --> $DIR/cpp20_rwc_syncs.rs:LL:CC
+ |
+LL | unsafe { std::hint::unreachable_unchecked(); }
+ | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+note: inside `main` at $DIR/cpp20_rwc_syncs.rs:LL:CC
+ --> $DIR/cpp20_rwc_syncs.rs:LL:CC
+ |
+LL | test_cpp20_rwc_syncs();
+ | ^^^^^^^^^^^^^^^^^^^^^^
+
+note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
+
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: deadlock: the evaluated program deadlocked
--> $DIR/libc_pthread_mutex_deadlock.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: unlocked a default mutex that was not locked by the current thread
--> $DIR/libc_pthread_mutex_wrong_owner.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: unlocked an rwlock that was not locked by the active thread
--> $DIR/libc_pthread_rwlock_read_wrong_owner.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: deadlock: the evaluated program deadlocked
--> $DIR/libc_pthread_rwlock_write_read_deadlock.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: deadlock: the evaluated program deadlocked
--> $DIR/libc_pthread_rwlock_write_write_deadlock.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: Undefined Behavior: unlocked an rwlock that was not locked by the active thread
--> $DIR/libc_pthread_rwlock_write_wrong_owner.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: unsupported operation: racy imperfectly overlapping atomic access is not possible in the C++20 memory model, and not supported by Miri's weak memory emulation
--> $DIR/racing_mixed_size.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
error: unsupported operation: racy imperfectly overlapping atomic access is not possible in the C++20 memory model, and not supported by Miri's weak memory emulation
--> $DIR/racing_mixed_size_read.rs:LL:CC
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
-error: aborting due to previous error; 1 warning emitted
+error: aborting due to previous error
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
thread '<unnamed>' panicked at 'Hello!', $DIR/simple.rs:LL:CC
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
thread 'childthread' panicked at 'Hello, world!', $DIR/simple.rs:LL:CC
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
Thread 1 starting, will block on mutex
Thread 1 reported it has started
thread '<unnamed>' panicked at 'panic in thread 2', $DIR/concurrent-panic.rs:LL:CC
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
Dropping 0
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-
+++ /dev/null
-warning: thread support is experimental: the scheduler is not preemptive, and can get stuck in spin loops.
- (see https://github.com/rust-lang/miri/issues/1388)
-