rust/tests/fail/stacked_borrows/pointer_smuggling.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/pointer_smuggling.rs:LL:CC
   |
LL |     let _x = unsafe { *PTR };
   |                       ^^^^
   |                       |
   |                       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..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/pointer_smuggling.rs:LL:CC
   |
LL |         PTR = x;
   |               ^
help: <TAG> was later invalidated at offsets [0x0..0x1] by a write access
  --> $DIR/pointer_smuggling.rs:LL:CC
   |
LL |     *val = 2; // this invalidates any raw ptrs `fun1` might have created.
   |     ^^^^^^^^
   = note: backtrace:
   = note: inside `fun2` at $DIR/pointer_smuggling.rs:LL:CC
note: inside `main` at $DIR/pointer_smuggling.rs:LL:CC
  --> $DIR/pointer_smuggling.rs:LL:CC
   |
LL |     fun2(); // if they now use a raw ptr they break our reference
   |     ^^^^^^

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 read 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/pointer_smuggling.rs:LL:CC`
			`\|`
			`LL \| let _x = unsafe { *PTR };`
			`\| ^^^^`
			`\| \|`
make permissive provenance and raw-ptr tagging the default 2022-06-26 20:14:18 -05:00			`\| attempting a read 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			`\| this error occurs as part of an access at ALLOC[0x0..0x1]`
			`\|`
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/pointer_smuggling.rs:LL:CC`
			`\|`
			`LL \| PTR = x;`
			`\| ^`
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 write access`
Add a custom ui test runner and move all tests to it 2022-03-17 08:49:10 -05:00			`--> $DIR/pointer_smuggling.rs:LL:CC`
			`\|`
			LL \| *val = 2; // this invalidates any raw ptrs `fun1` might have created.
			`\| ^^^^^^^^`
pointer tag tracking: on creation, log the offsets it is created for 2022-07-02 09:11:39 -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 `fun2` at $DIR/pointer_smuggling.rs:LL:CC
			note: inside `main` at $DIR/pointer_smuggling.rs:LL:CC
			`--> $DIR/pointer_smuggling.rs:LL:CC`
			`\|`
			`LL \| fun2(); // if they now use a raw ptr they break our reference`
			`\| ^^^^^^`

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

			`error: aborting due to previous error`