|
From: Nicholas N. <nj...@cs...> - 2005-02-11 19:54:42
|
On Fri, 11 Feb 2005, Jeremy Fitzhardinge wrote: >> I don't like the idea of --ignore-config. > > 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. Yes, I see that. I just don't want to add another CLO for a problem that could be solved by not using a CLO -- ie. if we explicitly put more CLOs in vg_regtest (CLOs on the command line always override those in .valgrindrc and VALGRIND_OPTS). But I may be swimming against the tide, here. N |