njn | e43d3ae | 2003-05-05 13:04:49 +0000 | [diff] [blame] | 1 | |
njn | e43d3ae | 2003-05-05 13:04:49 +0000 | [diff] [blame] | 2 | Building and not installing it |
| 3 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
njn | e43d3ae | 2003-05-05 13:04:49 +0000 | [diff] [blame] | 4 | |
njn | 090dc84 | 2005-03-12 16:47:07 +0000 | [diff] [blame] | 5 | To run Valgrind without having to install it, run coregrind/valgrind |
sewardj | 45f4e7c | 2005-09-27 19:20:21 +0000 | [diff] [blame] | 6 | with the VALGRIND_LIB environment variable set, where <dir> is the root |
njn | 090dc84 | 2005-03-12 16:47:07 +0000 | [diff] [blame] | 7 | of the source tree (and must be an absolute path). Eg: |
| 8 | |
sewardj | 45f4e7c | 2005-09-27 19:20:21 +0000 | [diff] [blame] | 9 | VALGRIND_LIB=~/grind/head4/.in_place ~/grind/head4/coregrind/valgrind |
njn | e43d3ae | 2003-05-05 13:04:49 +0000 | [diff] [blame] | 10 | |
| 11 | This allows you to compile and run with "make" instead of "make install", |
| 12 | saving you time. |
| 13 | |
| 14 | I recommend compiling with "make --quiet" to further reduce the amount of |
| 15 | output spewed out during compilation, letting you actually see any errors, |
| 16 | warnings, etc. |
| 17 | |
| 18 | |
| 19 | Running the regression tests |
| 20 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 21 | To build and run all the regression tests, run "make [--quiet] regtest". |
| 22 | |
| 23 | To run a subset of the regression tests, execute: |
| 24 | |
| 25 | perl tests/vg_regtest <name> |
| 26 | |
| 27 | where <name> is a directory (all tests within will be run) or a single |
| 28 | .vgtest test file, or the name of a program which has a like-named .vgtest |
| 29 | file. Eg: |
| 30 | |
| 31 | perl tests/vg_regtest memcheck |
| 32 | perl tests/vg_regtest memcheck/tests/badfree.vgtest |
| 33 | perl tests/vg_regtest memcheck/tests/badfree |
| 34 | |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 35 | |
| 36 | Debugging Valgrind with GDB |
| 37 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 38 | To debug the valgrind launcher program (<prefix>/bin/valgrind) just |
| 39 | run it under gdb in the normal way. |
nethercote | 4fffabd | 2004-11-02 09:13:12 +0000 | [diff] [blame] | 40 | |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 41 | Debugging the main body of the valgrind code (and/or the code for |
| 42 | a particular tool) requires a bit more trickery but can be achieved |
| 43 | without too much problem by following these steps: |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 44 | |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 45 | (1) Set VALGRIND_LAUNCHER to <prefix>/bin/valgrind: |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 46 | |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 47 | export VALGRIND_LAUNCHER=/usr/local/bin/valgrind |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 48 | |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 49 | (2) Run "gdb <prefix>/lib/valgrind/<platform>/<tool>": |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 50 | |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 51 | gdb /usr/local/lib/valgrind/ppc32-linux/lackey |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 52 | |
tom | 4a5223b | 2005-11-17 12:31:12 +0000 | [diff] [blame] | 53 | (3) Do "handle SIGSEGV SIGILL nostop noprint" in GDB to prevent GDB from |
| 54 | stopping on a SIGSEGV or SIGILL: |
| 55 | |
| 56 | (gdb) handle SIGILL SIGSEGV nostop noprint |
| 57 | |
| 58 | (4) Set any breakpoints you want and proceed as normal for gdb. The |
| 59 | macro VG_(FUNC) is expanded to vgPlain_FUNC, so If you want to set |
| 60 | a breakpoint VG_(do_exec), you could do like this in GDB: |
| 61 | |
| 62 | (gdb) b vgPlain_do_exec |
| 63 | |
| 64 | (5) Run the tool with required options: |
| 65 | |
| 66 | (gdb) run pwd |
nethercote | 16b59ee | 2004-10-09 15:59:05 +0000 | [diff] [blame] | 67 | |
njn | 585b8b3 | 2005-10-10 11:36:55 +0000 | [diff] [blame] | 68 | |
| 69 | Self-hosting |
| 70 | ~~~~~~~~~~~~ |
| 71 | To run Valgrind under Valgrind: |
| 72 | |
| 73 | (1) Check out 2 trees, "inner" and "outer". "inner" runs the app |
| 74 | directly and is what you will be profiling. "outer" does the |
| 75 | profiling. |
| 76 | |
| 77 | (2) Configure inner with --enable-inner and build/install as |
| 78 | usual. |
| 79 | |
| 80 | (3) Configure outer normally and build/install as usual. |
| 81 | |
| 82 | (4) Choose a very simple program (date) and try |
| 83 | |
njn | 86d6807 | 2005-11-12 19:07:45 +0000 | [diff] [blame] | 84 | outer/.../bin/valgrind --sim-hints=enable-outer --trace-children=yes \ |
njn | 585b8b3 | 2005-10-10 11:36:55 +0000 | [diff] [blame] | 85 | --tool=cachegrind -v inner/.../bin/valgrind --tool=none -v prog |
| 86 | |
njn | 7cce5b8 | 2005-11-16 20:12:22 +0000 | [diff] [blame] | 87 | If you omit the --trace-children=yes, you'll only monitor inner's launcher |
| 88 | program, not its stage2. |
| 89 | |
| 90 | The whole thing is fragile, confusing and slow, but it does work well enough |
| 91 | for you to get some useful performance data. The inner Valgrind has most of |
| 92 | its output (ie. those lines beginning with "==<pid>==") prefixed with a '>', |
| 93 | which helps a lot. |
njn | 15a6563 | 2005-10-10 11:43:14 +0000 | [diff] [blame] | 94 | |
| 95 | At the time of writing the allocator is not annotated with client requests |
| 96 | so Memcheck is not as useful as it could be. It also has not been tested |
| 97 | much, so don't be surprised if you hit problems. |
njn | 0dc09e8 | 2005-11-03 16:24:53 +0000 | [diff] [blame] | 98 | |
weidendo | 10e80e3 | 2006-05-01 01:49:28 +0000 | [diff] [blame^] | 99 | When using self-hosting with an outer callgrind tool, use '--pop-on-jump' |
| 100 | (on the outer). Otherwise, callgrind has much higher memory requirements. |
| 101 | |
njn | 0b5efe7 | 2005-11-10 03:40:36 +0000 | [diff] [blame] | 102 | |
njn | 0dc09e8 | 2005-11-03 16:24:53 +0000 | [diff] [blame] | 103 | Printing out problematic blocks |
| 104 | ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ |
| 105 | If you want to print out a disassembly of a particular block that |
| 106 | causes a crash, do the following. |
| 107 | |
| 108 | Try running with "--vex-guest-chase-thresh=0 --trace-flags=10000000 |
| 109 | --trace-notbelow=999999". This should print one line for each block |
| 110 | translated, and that includes the address. |
| 111 | |
| 112 | Then re-run with 999999 changed to the highest bb number shown. |
| 113 | This will print the one line per block, and also will print a |
| 114 | disassembly of the block in which the fault occurred. |