|
From: <sv...@va...> - 2011-01-04 23:46:15
|
Author: njn
Date: 2011-01-04 23:46:07 +0000 (Tue, 04 Jan 2011)
New Revision: 11491
Log:
Clarify some details about "possibly lost" heap blocks.
Modified:
trunk/docs/xml/FAQ.xml
trunk/memcheck/docs/mc-manual.xml
Modified: trunk/docs/xml/FAQ.xml
===================================================================
--- trunk/docs/xml/FAQ.xml 2011-01-04 21:09:14 UTC (rev 11490)
+++ trunk/docs/xml/FAQ.xml 2011-01-04 23:46:07 UTC (rev 11491)
@@ -528,8 +528,9 @@
</listitem>
<listitem>
<para>"possibly lost" means your program is leaking
- memory, unless you're doing funny things with pointers.
- This is sometimes reasonable. Use
+ memory, unless you're doing unusual things with pointers that could
+ cause them to point into the middle of an allocated block; see the
+ user manual for some possible causes. Use
<option>--show-possibly-lost=no</option> if you don't want to see
these reports.</para>
</listitem>
Modified: trunk/memcheck/docs/mc-manual.xml
===================================================================
--- trunk/memcheck/docs/mc-manual.xml 2011-01-04 21:09:14 UTC (rev 11490)
+++ trunk/memcheck/docs/mc-manual.xml 2011-01-04 23:46:07 UTC (rev 11491)
@@ -401,7 +401,11 @@
<itemizedlist>
<listitem>
<para>The pointer might have originally been a start-pointer and have been
- moved along deliberately (or not deliberately) by the program.</para>
+ moved along deliberately (or not deliberately) by the program. In
+ particular, this can happen if your program uses tagged pointers, i.e.
+ if it uses the bottom one, two or three bits of a pointer, which are
+ normally always zero due to alignment, in order to store extra
+ information.</para>
</listitem>
<listitem>
|