Document the --max-threads command line option.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@14934

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index cb02ba68b173c1d281888471de92e158cc06bcb6..b1009d5c90c4e27ae70333dc123fc0517ad5a6cc 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -1683,6 +1683,19 @@ that can report errors, e.g. Memcheck, but not Cachegrind.</para>
     </listitem>
   </varlistentry>
 
+  <varlistentry id="opt.max-threads" xreflabel="--max-threads">
+    <term>
+      <option><![CDATA[--max-threads=<number> [default: 500] ]]></option>
+    </term>
+    <listitem>
+      <para>By default, Valgrind can handle to up to 500 threads.
+      Occasionally, that number is too small. Use this option to
+      provide a different limit. E.g.
+      <computeroutput>--max-threads=3000</computeroutput>.
+      </para>
+    </listitem>
+  </varlistentry>
+
 </variablelist>
 <!-- end of xi:include in the manpage -->