From: Florian Krohm <florian@eich-krohm.de>
Date: Mon, 16 Feb 2015 21:55:52 +0000 (+0000)
Subject: Document the --max-threads command line option.
X-Git-Tag: svn/VALGRIND_3_11_0~658
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=071d18df0637be26dff4ac96917e35e428fcacd2;p=thirdparty%2Fvalgrind.git

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 cb02ba68b1..b1009d5c90 100644
--- 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 -->