nethercote | f4928da | 2004-06-15 10:54:40 +0000 | [diff] [blame] | 1 | usage: valgrind --tool=<toolname> [options] prog-and-args |
| 2 | |
| 3 | common user options for all Valgrind tools, with defaults in [ ]: |
| 4 | --tool=<name> Use the Valgrind tool named <name> |
nethercote | a76368b | 2004-06-16 11:56:29 +0000 | [diff] [blame^] | 5 | -h --help show this message |
nethercote | f4928da | 2004-06-15 10:54:40 +0000 | [diff] [blame] | 6 | --help-debug show this message, plus debugging options |
| 7 | --version show version |
| 8 | -q --quiet run silently; only print error msgs |
| 9 | -v --verbose be more verbose, incl counts of errors |
| 10 | --trace-children=no|yes Valgrind-ise child processes? [no] |
| 11 | --track-fds=no|yes Track open file descriptors? [no] |
| 12 | |
| 13 | uncommon user options for all Valgrind tools: |
| 14 | --run-libc-freeres=no|yes Free up glibc memory at exit? [yes] |
| 15 | --weird-hacks=hack1,hack2,... [none] |
nethercote | e2be7e6 | 2004-06-16 11:51:08 +0000 | [diff] [blame] | 16 | recognised hacks are: lax-ioctls |
nethercote | f4928da | 2004-06-15 10:54:40 +0000 | [diff] [blame] | 17 | --signal-polltime=<time> time, in mS, we should poll for signals. |
| 18 | Only applies for older kernels which need |
| 19 | signal routing [50] |
| 20 | --lowlat-signals=no|yes improve wake-up latency when a thread receives |
| 21 | a signal [no] |
| 22 | --lowlat-syscalls=no|yes improve wake-up latency when a thread's |
| 23 | syscall completes [no] |
| 24 | --pointercheck=no|yes enforce client address space limits [yes] |
| 25 | |
| 26 | user options for Valgrind tools that report errors: |
| 27 | --logfile-fd=<number> file descriptor for messages [2=stderr] |
| 28 | --logfile=<file> log messages to <file>.pid<pid> |
| 29 | --logsocket=ipaddr:port log messages to socket ipaddr:port |
| 30 | --demangle=no|yes automatically demangle C++ names? [yes] |
| 31 | --num-callers=<number> show <num> callers in stack traces [4] |
| 32 | --error-limit=no|yes stop showing new errors if too many? [yes] |
| 33 | --show-below-main=no|yes continue stack traces below main() [no] |
| 34 | --suppressions=<filename> suppress errors described in <filename> |
| 35 | --gen-suppressions=no|yes print suppressions for errors detected [no] |
| 36 | --db-attach=no|yes start debugger when errors detected? [no] |
| 37 | --db-command=<command> command to start debugger [gdb -nw %f %p] |
| 38 | --input-fd=<number> file descriptor for input [0=stdin] |
| 39 | |
| 40 | user options for Nulgrind: |
| 41 | (none) |
| 42 | |
| 43 | debugging options for all Valgrind tools: |
| 44 | --sanity-level=<number> level of sanity checking to do [1] |
| 45 | --single-step=no|yes translate each instr separately? [no] |
| 46 | --optimise=no|yes improve intermediate code? [yes] |
| 47 | --profile=no|yes profile? (tool must be built for it) [no] |
| 48 | --chain-bb=no|yes do basic-block chaining? [yes] |
| 49 | --branchpred=yes|no generate branch prediction hints [no] |
| 50 | --trace-codegen=<XXXXX> show generated code? (X = 0|1) [00000] |
| 51 | --trace-syscalls=no|yes show all system calls? [no] |
| 52 | --trace-signals=no|yes show signal handling details? [no] |
| 53 | --trace-symtab=no|yes show symbol table details? [no] |
| 54 | --trace-sched=no|yes show thread scheduler details? [no] |
| 55 | --trace-pthread=none|some|all show pthread event details? [none] |
| 56 | --wait-for-gdb=yes|no pause on startup to wait for gdb attach |
| 57 | |
| 58 | debugging options for Valgrind tools that report errors |
| 59 | --dump-error=<number> show translation for basic block associated |
| 60 | with <number>'th error context [0=show none] |
| 61 | |
| 62 | debugging options for Nulgrind: |
| 63 | (none) |
| 64 | |
| 65 | Extra options read from ~/.valgrindrc, $VALGRIND_OPTS, ./.valgrindrc |
| 66 | |
| 67 | Valgrind is Copyright (C) 2000-2004 Julian Seward |
| 68 | and licensed under the GNU General Public License, version 2. |
| 69 | Bug reports, feedback, admiration, abuse, etc, to: valgrind.kde.org. |
| 70 | |
| 71 | Tools are copyright and licensed by their authors. See each |
| 72 | tool's start-up message for more information. |
| 73 | |