From dea2377dd988869212f4a66f1a624cd6908e3a0f Mon Sep 17 00:00:00 2001
From: Nicholas Nethercote <njn@valgrind.org>
Date: Tue, 15 May 2007 03:59:23 +0000
Subject: [PATCH] Clarify --trace-children a little.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@6741
---
 docs/xml/manual-core.xml | 15 ++++++++++++---
 1 file changed, 12 insertions(+), 3 deletions(-)

diff --git a/docs/xml/manual-core.xml b/docs/xml/manual-core.xml
index 5658d3cb62..23b3f4a0f3 100644
--- 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>
 
-- 
2.47.2