|
From: Julian S. <js...@ac...> - 2005-02-11 17:19:24
|
> The trouble is that V can pick up command-line options from a variety of > places, but we want the V running in the test harness to be running with > a very specific set of options. I normally run with a ~/.valgrindrc > containing a few of my preferred defaults; it doesn't seem like a good > idea for the regtest valgrind to use them though. --ignore-config would > basically suppress all of V's use of env variables or files for options, > and only use the options explicitly on the command line. Hmm, yes, fair enough. Perhaps it is a good idea. I think the meaning isn't too clear from the flag name, tho. "config" is too vague a term. I was thinking --ignore-valgrindrc but then that doesn't make it clear that $VALGRIND_OPTS is also ignored. Hmm. How about --cmd-line-opts-only ? Hmm. Cumbersome. Any better suggestions for a name? J |