|
From: Tom H. <to...@co...> - 2006-01-21 16:35:37
|
In message <43D...@us...>
Dave Nomura <dc...@us...> wrote:
> 1. if I installed valgrind into /usr/local but want to run a newer SVN
> version against some program is it sufficient to invoke valgrind:
> <SVN dir>/coregrind/valgrind <my_program>
> or
> alias vg <SVN dir>/coregrind/valgrind
> vg <my_program>
> I know that there are other libraries/shared objects that valgrind
> accesses and I thought that it might depend on the path used to
> invoke
> valgrind. If I use the VALGRIND_LAUNCHER or VALGRIND_LIB variables
> (set to a different valgrind release) for debugging but forget to
> unset them am I at risk for possibly
> running a different version of valgrind than I intended?
You should never need to set VALGRIND_LAUNCHER as the launcher (ie
the valgrind binary) does that.
If you are running outside the location where you told configure
you would be installing it then you need to set VALGRIND_LIB or you
will wind up running the installed version. The other option is to
configure with --prefix=/tmp/valgrind-test or something and then do
a make install and run /tmp/valgrind-test/bin/valgrind which is
what I tend to do.
> 2. I've been using the svn command listed on your website to pull over a
> newer version of valgrind. This command pulls over the entire
> trunk/* tree. Is there a way to just incrementally pull the files
> that changed or is the granularity of SVN just the entire source
> tree?
Just use "svn update" to update an existing tree with the latest changes.
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|