diff options
| author | Evan Huus <eapache@gmail.com> | 2012-12-28 17:09:07 +0000 |
|---|---|---|
| committer | Evan Huus <eapache@gmail.com> | 2012-12-28 17:09:07 +0000 |
| commit | 5eacf33f1f579cd3a333b36cf0e411a3ddaf6ddb (patch) | |
| tree | 3c16701ea7b315119b964978310c7b39783b54ff /doc/README.wmem | |
| parent | 0c66691b92668caaf51aac05a8c30f85867571db (diff) | |
Update wmem documentation for the new allocator.
Use the strict allocator when fuzzing (at least until the fuzz-bot starts
running everything under valgrind).
svn path=/trunk/; revision=46829
Diffstat (limited to 'doc/README.wmem')
| -rw-r--r-- | doc/README.wmem | 5 |
1 files changed, 4 insertions, 1 deletions
diff --git a/doc/README.wmem b/doc/README.wmem index afba6025cd..63782085e9 100644 --- a/doc/README.wmem +++ b/doc/README.wmem @@ -140,6 +140,10 @@ The currently available allocators are: - WMEM_ALLOCATOR_BLOCK (wmem_allocator_block.*) A block allocator that grabs large chunks of memory at a time (8 MB currently) and serves allocations out of those chunks. + - WMEM_ALLOCATOR_STRICT (wmem_allocator_strict.*) + An allocator that does its best to find invalid memory usage via + things like canaries and scrubbing freed memory. Valgrind is the + better choice on platforms that support it. 3.2 Creating a Pool @@ -262,7 +266,6 @@ not yet implemented: - red-black tree - tvb_memdup - - canaries The following is a list of things that emem doesn't provide but that it might be nice if wmem did provide them: |