|
From: <sv...@va...> - 2005-10-10 11:43:49
|
Author: njn
Date: 2005-10-10 12:43:14 +0100 (Mon, 10 Oct 2005)
New Revision: 4897
Log:
clarify self-hosting instructions
Modified:
trunk/README_DEVELOPERS
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-10-10 11:36:55 UTC (rev 4896)
+++ trunk/README_DEVELOPERS 2005-10-10 11:43:14 UTC (rev 4897)
@@ -70,6 +70,10 @@
--tool=3Dcachegrind -v inner/.../bin/valgrind --tool=3Dnone -v pr=
og
=20
It's fragile, confusing and slow, but it does work well enough for
-you to get some useful performance data. At the time of writing
-the allocator is not annotated with client requests so Memcheck is
-not as useful as it could be.
+you to get some useful performance data. The inner Valgrind has most 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.
|