|
From: Rich C. <Ric...@me...> - 2005-03-09 22:10:09
|
On Sun, 27 Feb 2005 13:59:10 -0600 (CST) Nicholas Nethercote <nj...@cs...> wrote: > On Fri, 25 Feb 2005, Julian Seward wrote: > > >> And should we consider defaulting to memcheck again? > > > > Personally I would like that. I find it annoying to constantly > > have to type --tool=memcheck (but not _always_, so .valgrindrc > > isn't the answer). > > .valgrindrc works with that. I'm in the same situation, so I have > --tool=memcheck in my .valgrindrc, and if I want to run something else I > just put that on the command line; command line-specified options take > precedence over the .valgrindrc ones so it all just works. > .valgrindrc works great when you are running code as your self on your own box. When you are working on a target in a production type environment, there is no .valgrindrc. I'd vote for the default of --tool=memcheck. -- Rich Coe ric...@me... General Electric Healthcare Technologies Global Software Platfroms, Computer Technology Team |