|
From: Nicholas N. <nj...@ca...> - 2004-01-31 22:58:06
|
On Fri, 30 Jan 2004, Nicholas Nethercote wrote:
> I imagined this:
>
> common user options for all Valgrind tools, with defaults in [ ]:
> --tool=<name> Use the Valgrind tool named <name>
> --help show this message
> * --help-debug show this message, plus debugging options
Ok, that's done. However, there are still too many options, mostly
because of the uncommon options:
uncommon user options for all Valgrind tools:
--run-libc-freeres=no|yes Free up glibc memory at exit? [yes]
--weird-hacks=hack1,hack2,... [none]
recognised hacks are: ioctl-VTIME truncate-writes lax-ioctls
--signal-polltime=<time> time, in mS, we should poll for signals.
Only applies for older kernels which need
signal routing [50]
--lowlat-signals=no|yes improve wake-up latency when a thread receives
a signal [no]
--lowlat-syscalls=no|yes improve wake-up latency when a thread's
syscall completes [no]
--pointercheck=no|yes enforce client address space limits [yes]
Since they're all 0.1% cases, I think it would be nice to move all of them
into --weird-hacks (except --signal-polltime, which is hard to do since it
is not a boolean), eg:
uncommon user options for all Valgrind tools:
--weird-hacks=hack1,hack2,... [none]
recognised hacks are: ioctl-VTIME, truncate-writes, lax-ioctls,
libc-freeres, lowlat-sigs, lowlat-syscalls, no-ptrcheck
--signal-polltime=<time> time, in mS, we should poll for signals.
Only applies for older kernels which need
signal routing [50]
Of course, for backwards compatibility, we could let the old invocations
still work. The way --weird-hacks works internally would have to be
changed slightly, eg. into a bit-mask, because it currently only allows
one weird hack at a time.
Comments?
N
|