14e72e7ffa
Previous Stacked Borrows diagnostics were missing a lot of information about the state of the interpreter, and it was difficult to add additional state because it was threaded through all the intervening function signatures. This change factors a lot of the arguments which used to be passed individually to many stacked borrows functions into a single `DiagnosticCx`, which is built in `Stacks::for_each`, and since it wraps a handle to `AllocHistory`, we can now handle more nuanced things like heterogeneous borrow of `!Freeze` types.
29 lines
1.4 KiB
Plaintext
29 lines
1.4 KiB
Plaintext
error: Undefined Behavior: attempting a read access using <TAG> at ALLOC[0x0], but that tag does not exist in the borrow stack for this location
|
|
--> $DIR/illegal_write4.rs:LL:CC
|
|
|
|
|
LL | let _val = *reference;
|
|
| ^^^^^^^^^^
|
|
| |
|
|
| attempting a read access using <TAG> at ALLOC[0x0], but that tag does not exist in the borrow stack for this location
|
|
| this error occurs as part of an access at ALLOC[0x0..0x4]
|
|
|
|
|
= help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental
|
|
= help: see https://github.com/rust-lang/unsafe-code-guidelines/blob/master/wip/stacked-borrows.md for further information
|
|
help: <TAG> was created by a SharedReadOnly retag at offsets [0x0..0x4]
|
|
--> $DIR/illegal_write4.rs:LL:CC
|
|
|
|
|
LL | let reference = unsafe { &*raw }; // freeze
|
|
| ^^^^^
|
|
help: <TAG> was later invalidated at offsets [0x0..0x4] by a Unique retag
|
|
--> $DIR/illegal_write4.rs:LL:CC
|
|
|
|
|
LL | let _mut_ref: &mut i32 = unsafe { mem::transmute(raw) }; // &mut, with raw tag
|
|
| ^^^^^^^^^^^^^^^^^^^
|
|
= note: backtrace:
|
|
= note: inside `main` at $DIR/illegal_write4.rs:LL:CC
|
|
|
|
note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
|
|
|
|
error: aborting due to previous error
|
|
|