summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDaan <daan@microsoft.com>2020-09-14 09:13:20 -0700
committerGitHub <noreply@github.com>2020-09-14 09:13:20 -0700
commit5cd5423108604569c3dbc6c51a78bd86a574ab3a (patch)
tree6f4ff1955534c3621e23407709e41a932cf19685
parent0df0c17f5abf555bddbf2842ec700395667bd8b6 (diff)
parentb19bdfac872f2f5fd03ada55fc27f07f01e2a826 (diff)
Merge pull request #297 from Shivam7-1/patch-2
Updated readme.md
-rw-r--r--readme.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/readme.md b/readme.md
index ca94e7f..be6fddb 100644
--- a/readme.md
+++ b/readme.md
@@ -223,7 +223,7 @@ completely and redirect all calls to the _mimalloc_ library instead .
## Environment Options
You can set further options either programmatically (using [`mi_option_set`](https://microsoft.github.io/mimalloc/group__options.html)),
-or via environment variables.
+or via environment variables:
- `MIMALLOC_SHOW_STATS=1`: show statistics when the program terminates.
- `MIMALLOC_VERBOSE=1`: show verbose messages.
@@ -273,11 +273,11 @@ _mimalloc_ can be build in secure mode by using the `-DMI_SECURE=ON` flags in `c
to make mimalloc more robust against exploits. In particular:
- All internal mimalloc pages are surrounded by guard pages and the heap metadata is behind a guard page as well (so a buffer overflow
- exploit cannot reach into the metadata),
+ exploit cannot reach into the metadata).
- All free list pointers are
[encoded](https://github.com/microsoft/mimalloc/blob/783e3377f79ee82af43a0793910a9f2d01ac7863/include/mimalloc-internal.h#L396)
- with per-page keys which is used both to prevent overwrites with a known pointer, as well as to detect heap corruption,
-- Double free's are detected (and ignored),
+ with per-page keys which is used both to prevent overwrites with a known pointer, as well as to detect heap corruption.
+- Double free's are detected (and ignored).
- The free lists are initialized in a random order and allocation randomly chooses between extension and reuse within a page to
mitigate against attacks that rely on a predicable allocation order. Similarly, the larger heap blocks allocated by mimalloc
from the OS are also address randomized.