From: Julian Seward Date: Fri, 6 Oct 2006 11:47:01 +0000 (+0000) Subject: Expand the first para of the custom-allocator section so it says what X-Git-Tag: svn/VALGRIND_3_3_0~659 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=afc64cc112a88e7f3e8eaa5d963d223f3ff4dd21;p=thirdparty%2Fvalgrind.git Expand the first para of the custom-allocator section so it says what this section actually describes. git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6199 --- diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml index ed2a714267..8b0ca52191 100644 --- a/memcheck/docs/mc-manual.xml +++ b/memcheck/docs/mc-manual.xml @@ -1080,7 +1080,13 @@ arguments. Memory Pools: describing and working with custom allocators Some programs use custom memory allocators, often for performance -reasons. There are many different sorts of memory pool, so Memcheck +reasons. Left to itself, Memcheck is unable to "understand" the +behaviour of custom allocation schemes and so may miss errors and +leaks in your program. What this section describes is a way to give +Memcheck enough of a description of your custom allocator that it can +make at least some sense of what is happening. + +There are many different sorts of custom allocator, so Memcheck attempts to reason about them using a loose, abstract model. We use the following terminology when describing custom allocation systems: