|
From: <sv...@va...> - 2005-11-16 20:12:36
|
Author: njn
Date: 2005-11-16 20:12:22 +0000 (Wed, 16 Nov 2005)
New Revision: 5154
Log:
Minor tweaks.
Modified:
trunk/NEWS
trunk/README_DEVELOPERS
Modified: trunk/NEWS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/NEWS 2005-11-16 19:15:33 UTC (rev 5153)
+++ trunk/NEWS 2005-11-16 20:12:22 UTC (rev 5154)
@@ -51,14 +51,14 @@
=20
- It should build with gcc-2.96.
=20
-- 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.
=20
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.
=20
- The --tool flag is optional once again; if you omit it, Memcheck
is run by default.
@@ -66,9 +66,9 @@
- The --num-callers flag now has a default value of 12. It was
previously 4.
=20
-- 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=3Dyes 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.
=20
- The --gen-suppressions flag supports an "all" value that causes every
Modified: trunk/README_DEVELOPERS
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
--- trunk/README_DEVELOPERS 2005-11-16 19:15:33 UTC (rev 5153)
+++ trunk/README_DEVELOPERS 2005-11-16 20:12:22 UTC (rev 5154)
@@ -69,12 +69,14 @@
outer/.../bin/valgrind --sim-hints=3Denable-outer --trace-children=3D=
yes \
--tool=3Dcachegrind -v inner/.../bin/valgrind --tool=3Dnone -v pr=
og
=20
-If you omit the --trace-children=3Dyes, you'll only valgrind inner's lau=
ncher
-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 wit=
h
-"=3D=3D<pid>=3D=3D") prefixed with a '>', which helps a lot.
+If you omit the --trace-children=3Dyes, you'll only monitor inner's laun=
cher
+program, not its stage2.
=20
+The whole thing is fragile, confusing and slow, but it does work well en=
ough
+for you to get some useful performance data. The inner Valgrind has mos=
t of
+its output (ie. those lines beginning with "=3D=3D<pid>=3D=3D") prefixed=
with a '>',
+which helps a lot.
+
At the time of writing the allocator is not annotated with client reques=
ts
so Memcheck is not as useful as it could be. It also has not been teste=
d
much, so don't be surprised if you hit problems.
|