|
From: <br...@gi...> - 2006-01-01 03:44:08
|
There is a warning in the README: Important! Do not move the valgrind installation into a place different from that specified by --prefix at build time. This will cause things to break in subtle ways, mostly when Valgrind handles fork/exec calls. I generally cannot tolerate this restriction, so I went into the code to see what it would take to remove it, and I found the undocumented environment variable VALGRIND_LIB (which tells where Valgrind files live) and some code to determine at run time from what file the program was invoked. I didn't find the name of my "prefix" directory used anywhere except where subject to the VALGRIND_LIB environment variable. Does this mean the warning from the README is obsolete, or is the problem even more subtle? -- Bryan Henderson Phone 408-621-2000 San Jose, California |
|
From: Tom H. <to...@co...> - 2006-01-01 09:27:06
|
In message <E1E...@ma...>
br...@gi... (Bryan Henderson) wrote:
> There is a warning in the README:
>
> Important! Do not move the valgrind installation into a place
> different from that specified by --prefix at build time. This will
> cause things to break in subtle ways, mostly when Valgrind handles
> fork/exec calls.
>
> I generally cannot tolerate this restriction, so I went into the code
> to see what it would take to remove it, and I found the undocumented
> environment variable VALGRIND_LIB (which tells where Valgrind files
> live) and some code to determine at run time from what file the
> program was invoked. I didn't find the name of my "prefix" directory
> used anywhere except where subject to the VALGRIND_LIB environment
> variable. Does this mean the warning from the README is obsolete, or
> is the problem even more subtle?
It's not obsolete because we don't expect people to go round setting
that variable all the time.
Why do you want to be able to move valgrind around anyway?
Tom
--
Tom Hughes (to...@co...)
http://www.compton.nu/
|