Skip to content

Commit 1b9e19a

Browse files
clarify that a (tracked) tag may never be popped
Co-authored-by: Ralf Jung <[email protected]>
1 parent 672d721 commit 1b9e19a

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -383,7 +383,7 @@ to Miri failing to detect cases of undefined behavior in a program.
383383
Borrows "protectors". Specifying this argument multiple times does not overwrite the previous
384384
values, instead it appends its values to the list. Listing an id multiple times has no effect.
385385
* `-Zmiri-track-pointer-tag=<tag1>,<tag2>,...` shows a backtrace when a given pointer tag
386-
is created or when it is popped from a borrow stack (which is where the tag becomes invalid
386+
is created and when (if ever) it is popped from a borrow stack (which is where the tag becomes invalid
387387
and any future use of it will error). This helps you in finding out why UB is
388388
happening and where in your code would be a good place to look for it.
389389
Specifying this argument multiple times does not overwrite the previous

0 commit comments

Comments
 (0)