Make the freed-block-queue volume metrics 64-bit throughout, to avoid
any wierdness on very large machines in the future. Also, double the
default size from 5MB to 10MB, on the basis that programs are now on
average twice as lardy as they were when it was set to 5MB, whenever
that was.
git-svn-id: svn://svn.valgrind.org/valgrind/trunk@7256 a5019735-40e9-0310-863c-91ae7b9d1cf9
diff --git a/memcheck/docs/mc-manual.xml b/memcheck/docs/mc-manual.xml
index f8444c7..3ddcc2b 100644
--- a/memcheck/docs/mc-manual.xml
+++ b/memcheck/docs/mc-manual.xml
@@ -122,7 +122,7 @@
<varlistentry id="opt.freelist-vol" xreflabel="--freelist-vol">
<term>
- <option><![CDATA[--freelist-vol=<number> [default: 5000000] ]]></option>
+ <option><![CDATA[--freelist-vol=<number> [default: 10000000] ]]></option>
</term>
<listitem>
<para>When the client program releases memory using
@@ -137,7 +137,7 @@
have been freed.</para>
<para>This flag specifies the maximum total size, in bytes, of the
- blocks in the queue. The default value is five million bytes.
+ blocks in the queue. The default value is ten million bytes.
Increasing this increases the total amount of memory used by
<constant>memcheck</constant> but may detect invalid uses of freed
blocks which would otherwise go undetected.</para>