Clarify --trace-children a little.

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

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index 5658d3cb62c96e1d101fbb5da39cff88c2062aaa..23b3f4a0f344ffb484d7c8492e33efc9cd8ac413 100644 (file)
--- a/docs/xml/manual-core.xml
+++ b/docs/xml/manual-core.xml
@@ -640,9 +640,18 @@ categories.</para>
       <option><![CDATA[--trace-children=<yes|no> [default: no] ]]></option>
     </term>
     <listitem>
-      <para>When enabled, Valgrind will trace into child processes.
-      This can be confusing and isn't usually what you want, so it is
-      disabled by default.</para>
+      <para>When enabled, Valgrind will trace into sub-processes
+      initiated via the <varname>exec</varname> system call.  This can be
+      confusing and isn't usually what you want, so it is disabled by
+      default.  
+      </para>
+      <para>Note that Valgrind does trace into the child of a
+      <varname>fork</varname> (it would be difficult not too, since
+      <varname>fork</varname> makes an identical copy of a process), so this
+      option is arguably badly named.  However, most children of
+      <varname>fork</varname> calls immediately call <varname>exec</varname>
+      anyway.
+      </para>
     </listitem>
   </varlistentry>