You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
| ^^^^^^^^^^^^^^^^^^^^ sharing memory with a native function
@@ -10,25 +10,25 @@ LL | init_n(2, slice_ptr);
10
10
= help: what this means is that Miri will easily miss Undefined Behavior related to incorrect usage of this shared memory, so you should not take a clean Miri run as a signal that your FFI code is UB-free
11
11
= help: tracing memory accesses in native code is not yet fully implemented, so there can be further imprecisions beyond what is documented here
12
12
= note: BACKTRACE:
13
-
= note: inside `partial_init` at tests/native-lib/tracing/fail/partial_init.rs:LL:CC
13
+
= note: inside `partial_init` at tests/native-lib/fail/tracing/partial_init.rs:LL:CC
= help: what this means is that Miri will easily miss Undefined Behavior related to incorrect usage of this shared memory, so you should not take a clean Miri run as a signal that your FFI code is UB-free
11
11
= help: tracing memory accesses in native code is not yet fully implemented, so there can be further imprecisions beyond what is documented here
12
12
= note: BACKTRACE:
13
-
= note: inside `unexposed_reachable_alloc` at tests/native-lib/tracing/fail/unexposed_reachable_alloc.rs:LL:CC
13
+
= note: inside `unexposed_reachable_alloc` at tests/native-lib/fail/tracing/unexposed_reachable_alloc.rs:LL:CC
= help: this program is using integer-to-pointer casts or (equivalently) `ptr::with_exposed_provenance`, which means that Miri might miss pointer bugs in this program
27
-
= help: see https://doc.rust-lang.org/nightly/std/ptr/fn.with_exposed_provenance.html for more details on that operation
28
-
= help: to ensure that Miri does not miss bugs in your program, use Strict Provenance APIs (https://doc.rust-lang.org/nightly/std/ptr/index.html#strict-provenance, https://crates.io/crates/sptr) instead
29
-
= help: you can then set `MIRIFLAGS=-Zmiri-strict-provenance` to ensure you are not relying on `with_exposed_provenance` semantics
30
-
= help: alternatively, `MIRIFLAGS=-Zmiri-permissive-provenance` disables this warning
31
-
= note: BACKTRACE:
32
-
= note: inside `unexposed_reachable_alloc` at tests/native-lib/tracing/fail/unexposed_reachable_alloc.rs:LL:CC
error: Undefined Behavior: memory access failed: attempting to access 4 bytes, but got $HEX[noalloc] which is a dangling pointer (it has no provenance)
0 commit comments