Minor tweaks.

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

diff --git a/NEWS b/NEWS
index 76ee3147a0839a60950ffecc289ace49b5ffe56b..6dfec4b32f5680288232400fc6bff9f5613b0917 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -51,14 +51,14 @@ Other user-visible changes:
 
 - It should build with gcc-2.96.
 
-- Valgrind can now run itself (given some very-magical incantations).
+- Valgrind can now run itself (see README_DEVELOPERS for how).
   This is not much use to you, but it means the developers can now
   profile Valgrind using Cachegrind.  As a result a couple of
   performance bad cases have been fixed.
 
 The following are some user-visible changes that occurred in earlier
 versions that may not have been announced, or were announced but not
-widely realised.  So we're mentioning them now.
+widely noticed.  So we're mentioning them now.
 
 - The --tool flag is optional once again;  if you omit it, Memcheck
   is run by default.
@@ -66,9 +66,9 @@ widely realised.  So we're mentioning them now.
 - The --num-callers flag now has a default value of 12.  It was
   previously 4.
 
-- The --xml flag causes Valgrind's output to be produced in XML format.
-  This is designed to make it easy for other programs to consume
-  Valgrind's output.  The format is described in the file
+- The --xml=yes flag causes Valgrind's output to be produced in XML
+  format.  This is designed to make it easy for other programs to
+  consume Valgrind's output.  The format is described in the file
   docs/internals/xml-format.txt.
 
 - The --gen-suppressions flag supports an "all" value that causes every

diff --git a/README_DEVELOPERS b/README_DEVELOPERS
index d5f7a993165d787bf66e7b282923587c31e97b24..defce7859aeb6b6a3a065a00d236c76b9aa64cdd 100644 (file)
--- a/README_DEVELOPERS
+++ b/README_DEVELOPERS
@@ -69,11 +69,13 @@ To run Valgrind under Valgrind:
     outer/.../bin/valgrind --sim-hints=enable-outer --trace-children=yes  \
        --tool=cachegrind -v inner/.../bin/valgrind --tool=none -v prog
 
-If you omit the --trace-children=yes, you'll only valgrind inner's launcher
-program, not its stage2.  The whole thing is fragile, confusing and slow,
-but it does work well enough for you to get some useful performance data.
-The inner Valgrind has most of its output (ie. those lines beginning with
-"==<pid>==") prefixed with a '>', which helps a lot.
+If you omit the --trace-children=yes, you'll only monitor inner's launcher
+program, not its stage2.
+
+The whole thing is fragile, confusing and slow, but it does work well enough
+for you to get some useful performance data.  The inner Valgrind has most of
+its output (ie. those lines beginning with "==<pid>==") prefixed with a '>',
+which helps a lot.
 
 At the time of writing the allocator is not annotated with client requests
 so Memcheck is not as useful as it could be.  It also has not been tested