zenithsiz/ftmemsim-valgrind
1
0
Fork 0
mirror of https://github.com/Zenithsiz/ftmemsim-valgrind.git synced 2026-02-03 10:05:29 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Clarify some details about "possibly lost" heap blocks.

Browse Source 
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11491
This commit is contained in:
Nicholas Nethercote 2011-01-04 23:46:07 +00:00
parent c3ff44e6e9
commit 71e0b2a3f8
2 changed files with 8 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
docs/xml/FAQ.xml
View File

@ -528,8 +528,9 @@ int main(void)
</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>

6
memcheck/docs/mc-manual.xml
View File

@ -401,7 +401,11 @@ three ways we know of that an interior-pointer can occur:</para>
<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>