doylet/ASANManualPoisoning
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Tweak wording of readme

Browse Source
This commit is contained in:
doyle 2023-08-28 23:41:56 +10:00
parent d2e3722772
commit 6cbd672a3e
2 changed files with 6 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
asan_example.cpp
View File

@ -105,12 +105,11 @@ int main()
"\n"
"We use a stack-allocated 16 byte array and test un/poisoning\n"
"various ranges of bytes from different alignments to clarify the\n"
"poisoning behaviour of the API.\n"
"\n"
"This reveals that calling the API haphazardly, unaligned or\n"
"straddling boundaries can lead to gaps in poisoned memory and hide\n"
"potential leaks (as also demonstrated in [Manual ASAN poisoning and\n"
"alignment](https://github.com/mcgov/asan_alignment_example)).\n"
"poisoning behaviour of the API. This reveals that calling the API\n"
"haphazardly, unaligned or straddling boundaries can lead to gaps in\n"
"poisoned memory and hide potential leaks (as also demonstrated in\n"
"[Manual ASAN poisoning and alignment]"
"(https://github.com/mcgov/asan_alignment_example)).\n"
"\n"
"## References\n"
"\n"

3
readme.md
View File

@ -47,8 +47,7 @@ poisoning behaviour of the API.
This reveals that calling the API haphazardly, unaligned or
straddling boundaries can lead to gaps in poisoned memory and hide
potential leaks (as also demonstrated in [Manual ASAN poisoning and
alignment](https://github.com/mcgov/asan_alignment_example) example
by `mcgov`.
alignment](https://github.com/mcgov/asan_alignment_example)).
## References