rust/tests/fail/stacked_borrows/illegal_write_despite_exposed1.stderr

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_write_despite_exposed1.rs:LL:CC
   |
LL |         let _val = *root2;
   |                    ^^^^^^
   |                    |
   |                    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_write_despite_exposed1.rs:LL:CC
   |
LL |         let root2 = &*exposed_ptr;
   |                     ^^^^^^^^^^^^^
help: <TAG> was later invalidated at offsets [0x0..0x4] by a write access
  --> $DIR/illegal_write_despite_exposed1.rs:LL:CC
   |
LL |         *exposed_ptr = 0;
   |         ^^^^^^^^^^^^^^^^
   = note: BACKTRACE:
   = note: inside `main` at $DIR/illegal_write_despite_exposed1.rs:LL:CC

note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

error: aborting due to previous error
implement 'delimited' expose tracking so we still detect some UB 2022-06-24 18:45:35 -05:00			`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_write_despite_exposed1.rs:LL:CC`
			`\|`
			`LL \| let _val = *root2;`
			`\| ^^^^^^`
			`\| \|`
			`\| 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`
Improve information sharing across SB diagnostics 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. 2022-05-22 18:39:09 -05:00			`help: <TAG> was created by a SharedReadOnly retag at offsets [0x0..0x4]`
			`--> $DIR/illegal_write_despite_exposed1.rs:LL:CC`
			`\|`
			`LL \| let root2 = &*exposed_ptr;`
			`\| ^^^^^^^^^^^^^`
			`help: <TAG> was later invalidated at offsets [0x0..0x4] by a write access`
			`--> $DIR/illegal_write_despite_exposed1.rs:LL:CC`
			`\|`
			`LL \| *exposed_ptr = 0;`
			`\| ^^^^^^^^^^^^^^^^`
make backtrace header a bit more visible 2022-08-31 07:51:05 -05:00			`= note: BACKTRACE:`
implement 'delimited' expose tracking so we still detect some UB 2022-06-24 18:45:35 -05:00			= note: inside `main` at $DIR/illegal_write_despite_exposed1.rs:LL:CC

			note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace

			`error: aborting due to previous error`