rust/tests/fail/stacked_borrows/box_exclusive_violation1.stderr

error: Undefined Behavior: attempting a write access using <TAG> at ALLOC[0x0], but that tag does not exist in the borrow stack for this location
  --> $DIR/box_exclusive_violation1.rs:LL:CC
   |
LL |         *LEAK = 7;
   |         ^^^^^^^^^
   |         |
   |         attempting a write 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/box_exclusive_violation1.rs:LL:CC
   |
LL |         LEAK = x as *const _ as *mut _;
   |                ^
help: <TAG> was later invalidated at offsets [0x0..0x4] by a write access
  --> $DIR/box_exclusive_violation1.rs:LL:CC
   |
LL |     *our = 5;
   |     ^^^^^^^^
   = note: BACKTRACE:
   = note: inside `unknown_code_2` at $DIR/box_exclusive_violation1.rs:LL:CC
note: inside `demo_box_advanced_unique` at $DIR/box_exclusive_violation1.rs:LL:CC
  --> $DIR/box_exclusive_violation1.rs:LL:CC
   |
LL |     unknown_code_2();
   |     ^^^^^^^^^^^^^^^^
note: inside `main` at $DIR/box_exclusive_violation1.rs:LL:CC
  --> $DIR/box_exclusive_violation1.rs:LL:CC
   |
LL |     demo_box_advanced_unique(Box::new(0));
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

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

error: aborting due to previous error
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			`error: Undefined Behavior: attempting a write access using <TAG> 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_exclusive_violation1.rs:LL:CC`
			`\|`
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			`LL \| *LEAK = 7;`
			`\| ^^^^^^^^^`
			`\| \|`
			`\| attempting a write 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]`
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 SharedReadOnly retag at offsets [0x0..0x4]`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`--> $DIR/box_exclusive_violation1.rs:LL:CC`
			`\|`
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			`LL \| LEAK = x as const _ as mut _;`
			`\| ^`
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..0x4] by a write access`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`--> $DIR/box_exclusive_violation1.rs:LL:CC`
			`\|`
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			`LL \| *our = 5;`
			`\| ^^^^^^^^`
make backtrace header a bit more visible 2022-08-31 07:51:05 -05:00			`= note: BACKTRACE:`
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			= note: inside `unknown_code_2` at $DIR/box_exclusive_violation1.rs:LL:CC
use ui_test regex capabilities 2022-07-13 17:59:33 -05:00			note: inside `demo_box_advanced_unique` at $DIR/box_exclusive_violation1.rs:LL:CC
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			`--> $DIR/box_exclusive_violation1.rs:LL:CC`
			`\|`
			`LL \| unknown_code_2();`
			`\| ^^^^^^^^^^^^^^^^`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			note: inside `main` at $DIR/box_exclusive_violation1.rs:LL:CC
			`--> $DIR/box_exclusive_violation1.rs:LL:CC`
			`\|`
use ui_test regex capabilities 2022-07-13 17:59:33 -05:00			`LL \| demo_box_advanced_unique(Box::new(0));`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`

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

			`error: aborting due to previous error`