From: Nicholas Nethercote Date: Tue, 4 Jan 2011 23:49:35 +0000 (+0000) Subject: Merge from trunk, r11491 (tweak docs on "possibly lost" leaks). X-Git-Tag: svn/VALGRIND_3_6_1~25 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=77a030a0f0980dd450177919df987ace833e05ee;p=thirdparty%2Fvalgrind.git Merge from trunk, r11491 (tweak docs on "possibly lost" leaks). git-svn-id: svn://svn.valgrind.org/valgrind/branches/VALGRIND_3_6_BRANCH@11492 --- diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml index 983e02adde..af197f856c 100644 --- a/docs/xml/FAQ.xml +++ b/docs/xml/FAQ.xml @@ -528,8 +528,9 @@ int main(void) "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 if you don't want to see these reports. diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml index c380fce2b3..8fd88b487b 100644 --- a/memcheck/docs/mc-manual.xml +++ b/memcheck/docs/mc-manual.xml @@ -401,7 +401,11 @@ three ways we know of that an interior-pointer can occur: The pointer might have originally been a start-pointer and have been - moved along deliberately (or not deliberately) by the program. + 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.