]> git.lizzy.rs Git - rust.git/blob - src/tools/miri/tests/fail/data_race/relax_acquire_race.stderr
attempt to clarify what the backtrace belongs to when there could be ambiguity
[rust.git] / src / tools / miri / tests / fail / data_race / relax_acquire_race.stderr
1 error: Undefined Behavior: Data race detected between (1) Read on thread `<unnamed>` and (2) Write on thread `<unnamed>` at ALLOC. (1) just happened here
2   --> $DIR/relax_acquire_race.rs:LL:CC
3    |
4 LL |                 *c.0
5    |                 ^^^^ Data race detected between (1) Read on thread `<unnamed>` and (2) Write on thread `<unnamed>` at ALLOC. (1) just happened here
6    |
7 help: and (2) occurred earlier here
8   --> $DIR/relax_acquire_race.rs:LL:CC
9    |
10 LL |             *c.0 = 1;
11    |             ^^^^^^^^
12    = help: this indicates a bug in the program: it performed an invalid operation, and caused Undefined Behavior
13    = help: see https://doc.rust-lang.org/nightly/reference/behavior-considered-undefined.html for further information
14    = note: BACKTRACE (of the first span):
15    = note: inside closure at $DIR/relax_acquire_race.rs:LL:CC
16
17 note: some details are omitted, run with `MIRIFLAGS=-Zmiri-backtrace=full` for a verbose backtrace
18
19 error: aborting due to previous error
20