From a2838e5fe1ac5d06bcc0894eb4be3151deee2a39 Mon Sep 17 00:00:00 2001
From: Nicholas Nethercote <n.nethercote@gmail.com>
Date: Thu, 22 Jul 2004 08:57:50 +0000
Subject: [PATCH] In response to bug #85665, clarify what --trace-children=yes
 does.

git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2521
---
 coregrind/docs/coregrind_core.html | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/coregrind/docs/coregrind_core.html b/coregrind/docs/coregrind_core.html
index 13f121c535..614dd33f35 100644
--- a/coregrind/docs/coregrind_core.html
+++ b/coregrind/docs/coregrind_core.html
@@ -522,8 +522,14 @@ These options work with all tools.
   <li><code>--trace-children=no</code> [default]<br>
       <code>--trace-children=yes</code>
       <p>When enabled, Valgrind will trace into child processes.  This
-      is confusing and usually not what you want, so is disabled by
+      is confusing and often not what you want, so is disabled by
       default.
+
+      <p>Note that the name of this option is slightly misleading.
+      It actually controls whether programs started with
+      <code>exec()</code> are run under Valgrind's control.  If your
+      program calls <code>fork()</code>, both the parent and the child
+      will run under Valgrind's control.
       </li><br><p>
 
   <li><code>--log-fd=&lt;number&gt;</code> [default: 2, stderr]
-- 
2.47.2