From: Nicholas Nethercote Date: Thu, 10 Nov 2005 03:40:36 +0000 (+0000) Subject: need --trace-children when self-hosting X-Git-Tag: svn/VALGRIND_3_1_0~168 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=95ff6df5b72dc4cc99e3ca6d7a3972b78e6bd826;p=thirdparty%2Fvalgrind.git need --trace-children when self-hosting git-svn-id: svn://svn.valgrind.org/valgrind/trunk@5064 --- diff --git a/README_DEVELOPERS b/README_DEVELOPERS index 798c47c149..f05b8485e1 100644 --- a/README_DEVELOPERS +++ b/README_DEVELOPERS @@ -66,18 +66,20 @@ To run Valgrind under Valgrind: (4) Choose a very simple program (date) and try - outer/.../bin/valgrind --weird-hacks=enable-outer \ + outer/.../bin/valgrind --weird-hacks=enable-outer --trace-children=yes \ --tool=cachegrind -v inner/.../bin/valgrind --tool=none -v prog -It's 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 "====") prefixed with a -'>', which helps a lot. +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 +"====") 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 much, so don't be surprised if you hit problems. + Printing out problematic blocks ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you want to print out a disassembly of a particular block that