|
From: <sv...@va...> - 2007-05-15 03:59:25
|
Author: njn
Date: 2007-05-15 04:59:23 +0100 (Tue, 15 May 2007)
New Revision: 6741
Log:
Clarify --trace-children a little.
Modified:
trunk/docs/xml/manual-core.xml
Modified: trunk/docs/xml/manual-core.xml
===================================================================
--- trunk/docs/xml/manual-core.xml 2007-05-14 14:06:30 UTC (rev 6740)
+++ trunk/docs/xml/manual-core.xml 2007-05-15 03:59:23 UTC (rev 6741)
@@ -640,9 +640,18 @@
<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>
|