tests/genmc/fail/data_race/atomic_ptr_dealloc_write_race.stderr

Running GenMC Verification...
error: Undefined Behavior: memory access failed: ALLOC has been freed, so this pointer is dangling
  --> tests/genmc/fail/data_race/atomic_ptr_dealloc_write_race.rs:LL:CC
   |
LL |                 *ptr = 42;
   |                 ^^^^^^^^^ Undefined Behavior occurred here
   |
   = 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
help: ALLOC was allocated here:
  --> tests/genmc/fail/data_race/atomic_ptr_dealloc_write_race.rs:LL:CC
   |
LL |                 let mut z: u64 = 1234;
   |                     ^^^^^
help: ALLOC was deallocated here:
  --> tests/genmc/fail/data_race/atomic_ptr_dealloc_write_race.rs:LL:CC
   |
LL |             }),
   |             ^
   = note: this is on thread `unnamed-ID`
   = note: stack backtrace:
           0: miri_start::{closure#1}
               at tests/genmc/fail/data_race/atomic_ptr_dealloc_write_race.rs:LL:CC
           1: <std::boxed::Box<{closure@tests/genmc/fail/data_race/atomic_ptr_dealloc_write_race.rs:LL:CC}> as std::ops::FnOnce<()>>::call_once
               at RUSTLIB/alloc/src/boxed.rs:LL:CC
           2: genmc::spawn_pthread_closure::thread_func
               at tests/genmc/fail/data_race/../../../utils/genmc.rs:LL:CC
note: the last function in that backtrace got called indirectly due to this code
  --> tests/genmc/fail/data_race/../../../utils/genmc.rs:LL:CC
   |
LL | /         libc::pthread_create(
LL | |             &raw mut thread_id,
LL | |             attr,
LL | |             thread_func::<F>,
LL | |             Box::into_raw(f) as *mut c_void,
LL | |         )
   | |_________^

note: add `-Zmiri-genmc-print-genmc-output` to MIRIFLAGS to see the detailed GenMC error report

error: aborting due to 1 previous error