|
From: <sv...@va...> - 2005-10-10 11:36:53
|
Author: njn Date: 2005-10-10 12:36:55 +0100 (Mon, 10 Oct 2005) New Revision: 4896 Log: Document self-hosting. 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-08 18:01:54 UTC (rev 4895) +++ trunk/README_DEVELOPERS 2005-10-10 11:36:55 UTC (rev 4896) @@ -50,3 +50,26 @@ =20 jump *$eip =20 + +Self-hosting +~~~~~~~~~~~~ +To run Valgrind under Valgrind: + +(1) Check out 2 trees, "inner" and "outer". "inner" runs the app + directly and is what you will be profiling. "outer" does the + profiling. + +(2) Configure inner with --enable-inner and build/install as + usual. + +(3) Configure outer normally and build/install as usual. + +(4) Choose a very simple program (date) and try + + outer/.../bin/valgrind --weird-hacks=3Denable-outer \ + --tool=3Dcachegrind -v inner/.../bin/valgrind --tool=3Dnone -v pr= og + +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. |