Re: [Valgrind-developers] tool-specific CLOs

[Nicholas N. <nj...@ca...>]

On Thu, 8 Jan 2004, Jeremy Fitzhardinge wrote:

> No, but if it isn't, then just don't look for the file.  There's no
> point in getting too heroic over it.

Yeah, I'll do that.

> It might also be useful to look in "." as well, since you might want a
> program-specific config file.  Or perhaps have an env var for looking
> for multiple config files?  Is this getting all too complex?

I'm currently looking in three places:

 1.  ~/.valgrindrc
 2.  VALGRIND_OPTS
 3.  ./.valgrindrc

Args are added in that order, the idea being that more 'local' args are
added later, to override less local ones.  (1) and (2) could be swapped,
but (3) should definitely be last, as it's clearly the most local.

N