rust/tests/fail/stacked_borrows/interior_mut1.stderr

error: Undefined Behavior: trying to retag from <TAG> for SharedReadWrite permission at ALLOC[0x0], but that tag does not exist in the borrow stack for this location
  --> $DIR/interior_mut1.rs:LL:CC
   |
LL |         let _val = *inner_shr.get();
   |                     ^^^^^^^^^^^^^^^
   |                     |
   |                     trying to retag from <TAG> for SharedReadWrite permission at ALLOC[0x0], but that tag does not exist in the borrow stack for this location
   |                     this error occurs as part of retag 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 SharedReadWrite retag at offsets [0x0..0x4]
  --> $DIR/interior_mut1.rs:LL:CC
   |
LL |         let inner_shr = &*inner_uniq; // adds a SharedReadWrite
   |                         ^^^^^^^^^^^^
help: <TAG> was later invalidated at offsets [0x0..0x4] by a write access
  --> $DIR/interior_mut1.rs:LL:CC
   |
LL |         *c.get() = UnsafeCell::new(1); // invalidates inner_shr
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   = note: BACKTRACE:
   = note: inside `main` at $DIR/interior_mut1.rs:LL:CC

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

error: aborting due to previous error
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 19:39:09 -04:00			`error: Undefined Behavior: trying to retag from <TAG> for SharedReadWrite permission at ALLOC[0x0], but that tag does not exist in the borrow stack for this location`
Add a custom ui test runner and move all tests to it 2022-03-17 13:49:10 +00:00			`--> $DIR/interior_mut1.rs:LL:CC`
			`\|`
Bless stderr files after rustfmt 2022-06-20 23:49:55 -07:00			`LL \| let _val = *inner_shr.get();`
			`\| ^^^^^^^^^^^^^^^`
			`\| \|`
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 19:39:09 -04:00			`\| trying to retag from <TAG> for SharedReadWrite permission at ALLOC[0x0], but that tag does not exist in the borrow stack for this location`
			`\| this error occurs as part of retag at ALLOC[0x0..0x4]`
Add a custom ui test runner and move all tests to it 2022-03-17 13:49:10 +00:00			`\|`
bless 2022-06-11 22:34:01 -07:00			`= help: this indicates a potential bug in the program: it performed an invalid operation, but the Stacked Borrows rules it violated are still experimental`
Add a custom ui test runner and move all tests to it 2022-03-17 13:49:10 +00:00			`= 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 19:39:09 -04:00			`help: <TAG> was created by a SharedReadWrite retag at offsets [0x0..0x4]`
Add a custom ui test runner and move all tests to it 2022-03-17 13:49:10 +00:00			`--> $DIR/interior_mut1.rs:LL:CC`
			`\|`
Bless stderr files after rustfmt 2022-06-20 23:49:55 -07:00			`LL \| let inner_shr = &*inner_uniq; // adds a SharedReadWrite`
			`\| ^^^^^^^^^^^^`
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 19:39:09 -04:00			`help: <TAG> was later invalidated at offsets [0x0..0x4] by a write access`
Add a custom ui test runner and move all tests to it 2022-03-17 13:49:10 +00:00			`--> $DIR/interior_mut1.rs:LL:CC`
			`\|`
Bless stderr files after rustfmt 2022-06-20 23:49:55 -07:00			`LL \| *c.get() = UnsafeCell::new(1); // invalidates inner_shr`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
make backtrace header a bit more visible 2022-08-31 14:51:05 +02:00			`= note: BACKTRACE:`
Add a custom ui test runner and move all tests to it 2022-03-17 13:49:10 +00:00			= note: inside `main` at $DIR/interior_mut1.rs:LL:CC

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

			`error: aborting due to previous error`