|
From: <sv...@va...> - 2006-10-06 11:47:08
|
Author: sewardj Date: 2006-10-06 12:47:01 +0100 (Fri, 06 Oct 2006) New Revision: 6199 Log: Expand the first para of the custom-allocator section so it says what this section actually describes. Modified: trunk/memcheck/docs/mc-manual.xml Modified: trunk/memcheck/docs/mc-manual.xml =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D --- trunk/memcheck/docs/mc-manual.xml 2006-10-06 11:45:00 UTC (rev 6198) +++ trunk/memcheck/docs/mc-manual.xml 2006-10-06 11:47:01 UTC (rev 6199) @@ -1080,7 +1080,13 @@ <title>Memory Pools: describing and working with custom allocators</titl= e> =20 <para>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.</para> + +<para>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:</para> |