rust/tests/fail/box-cell-alias.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/box-cell-alias.rs:LL:CC
   |
LL |     unsafe { (*ptr).set(20) };
   |              ^^^^^^^^^^^^^^
   |              |
   |              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..0x1]
   |
   = 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..0x1]
  --> $DIR/box-cell-alias.rs:LL:CC
   |
LL |     let ptr: *const Cell<u8> = &*val;
   |                                ^^^^^
help: <TAG> was later invalidated at offsets [0x0..0x1] by a Unique retag
  --> $DIR/box-cell-alias.rs:LL:CC
   |
LL |     let res = helper(val, ptr);
   |                      ^^^
   = note: BACKTRACE:
   = note: inside `helper` at $DIR/box-cell-alias.rs:LL:CC
note: inside `main` at $DIR/box-cell-alias.rs:LL:CC
  --> $DIR/box-cell-alias.rs:LL:CC
   |
LL |     let res = helper(val, ptr);
   |               ^^^^^^^^^^^^^^^^

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 18:39:09 -05: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 08:49:10 -05:00			`--> $DIR/box-cell-alias.rs:LL:CC`
			`\|`
make a bunch of tests look more like how they did before rustfmt 2022-06-25 22:30:29 -05:00			`LL \| unsafe { (*ptr).set(20) };`
			`\| ^^^^^^^^^^^^^^`
			`\| \|`
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			`\| 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..0x1]`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`\|`
bless 2022-06-12 00:34:01 -05: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 08:49:10 -05: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 18:39:09 -05:00			`help: <TAG> was created by a SharedReadWrite retag at offsets [0x0..0x1]`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`--> $DIR/box-cell-alias.rs:LL:CC`
			`\|`
			`LL \| let ptr: const Cell<u8> = &val;`
			`\| ^^^^^`
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 later invalidated at offsets [0x0..0x1] by a Unique retag`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`--> $DIR/box-cell-alias.rs:LL:CC`
			`\|`
			`LL \| let res = helper(val, ptr);`
			`\| ^^^`
make backtrace header a bit more visible 2022-08-31 07:51:05 -05:00			`= note: BACKTRACE:`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			= note: inside `helper` at $DIR/box-cell-alias.rs:LL:CC
			note: inside `main` at $DIR/box-cell-alias.rs:LL:CC
			`--> $DIR/box-cell-alias.rs:LL:CC`
			`\|`
			`LL \| let res = helper(val, ptr);`
			`\| ^^^^^^^^^^^^^^^^`

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

			`error: aborting due to previous error`