summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authornjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2011-01-04 23:46:07 +0000
committernjn <njn@a5019735-40e9-0310-863c-91ae7b9d1cf9>2011-01-04 23:46:07 +0000
commit7c02ba7c0457974d64ec661270d5bc42fcf59ef0 (patch)
tree912ab99c9c85a885d72a921b51f1e6cec7f19341 /docs
parentd2b78a660ea0dabaa8e2b7256740ffe94c9b87e6 (diff)
Clarify some details about "possibly lost" heap blocks.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@11491 a5019735-40e9-0310-863c-91ae7b9d1cf9
Diffstat (limited to 'docs')
-rw-r--r--docs/xml/FAQ.xml5
1 files changed, 3 insertions, 2 deletions
diff --git a/docs/xml/FAQ.xml b/docs/xml/FAQ.xml
index 983e02ad..af197f85 100644
--- a/docs/xml/FAQ.xml
+++ b/docs/xml/FAQ.xml
@@ -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>