commit 1d44709c4ca72cc0b86650fe19407d92dca47012
author nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Sun Feb 01 17:29:59 2004 +0000
committer nethercote <nethercote@a5019735-40e9-0310-863c-91ae7b9d1cf9> Sun Feb 01 17:29:59 2004 +0000
tree bfb5c30a61003f93ff49f8876aeda33c6f2b521a
parent 6c999f21def3633b957c43baee74163e607328de

Killed the terminally wounded --stop-after option.


git-svn-id: svn://svn.valgrind.org/valgrind/trunk@2238 a5019735-40e9-0310-863c-91ae7b9d1cf9

FAQ.txt

diff --git a/FAQ.txt b/FAQ.txt
index 61df533..818ae6f 100644
--- a/FAQ.txt
+++ b/FAQ.txt
@@ -199,9 +199,8 @@
      VG_ARGS variables.  Zeroing them will break things.
 
      As of 1.9.6, Valgrind only uses these variables with
-     --trace-children=no, when executing execve() or using the
-     --stop-after=yes flag.  This should reduce the potential for
-     problems.
+     --trace-children=no or when executing execve().  This should 
+     reduce the potential for problems.
 
 -----------------------------------------------------------------