attempt to clarify what the backtrace belongs to when there could be ambiguity

[rust.git] / src / tools / miri / tests / fail / stacked_borrows / illegal_write_despite_exposed1.stderr

diff --git a/src/tools/miri/tests/fail/stacked_borrows/illegal_write_despite_exposed1.stderr b/src/tools/miri/tests/fail/stacked_borrows/illegal_write_despite_exposed1.stderr
index 87ddf61d7586cfdd8d0ad68aac873412b1b4af6d..1bb3afe483ebad8c8546275e0d693ecc0fad57f8 100644 (file)
--- a/src/tools/miri/tests/fail/stacked_borrows/illegal_write_despite_exposed1.stderr
+++ b/src/tools/miri/tests/fail/stacked_borrows/illegal_write_despite_exposed1.stderr
@@ -19,7 +19,7 @@ help: <TAG> was later invalidated at offsets [0x0..0x4] by a write access
    |
 LL |         *exposed_ptr = 0;
    |         ^^^^^^^^^^^^^^^^
-   = note: BACKTRACE:
+   = note: BACKTRACE (of the first span):
    = 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