You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ This is a drop-in replacement for OS memory allocator that can be used to detect
5
5
* Your code contains inline assembly or links to proprietary libraries that cannot be instrumented by MSAN
6
6
* You want to find vulnerabilities in black-box binaries that you do not have the source code for (not always straightforward, see below)
7
7
* You want to check if the bug MSAN found is actually exploitable, i.e. if the uninitialized memory contents actually show up in the output
8
-
* You're debugging code that is specific to an exotic CPU architecture or operating sysem where MSAN is not available, such as macOS. If you're on a really obscure platform that doesn't have a Rust compiler, a less robust [C99 implementation](https://github.com/Shnatsel/libdiffuzz-c99) is available.
8
+
* You're debugging code that is specific to an exotic CPU architecture or operating system where MSAN is not available, such as macOS. If you're on a really obscure platform that doesn't have a Rust compiler, a less robust [C99 implementation](https://github.com/Shnatsel/libdiffuzz-c99) is available.
9
9
10
10
**This is not a drop-in replacement for Memory Sanitizer!** It will likely require changes to your code or your testing setup, see below.
0 commit comments