|
From: Josef W. <Jos...@gm...> - 2005-10-15 18:21:04
|
On Saturday 15 October 2005 18:32, Tom Hughes wrote:
> All the launcher does is decided which tool to run and exec it - there
> should be no need for a tool writer to recreate the launcher as it will
> try and run unknown tools quite happily.
Yes.
But as I said, I saw it as a big plus for the static linking of tools to be
able to install them without needing any valgrind installation at all.
No need to worry about version mismatches.
Can you ensure that the launcher from say VG 3.2 will
work flawlessly with callgrind linked with VG 3.1 ?
If not, external tools still would need to have a
version check at runtime as we have now.
I can get rid of this problem if I provide my own launcher ("callgrind").
BTW: Is a launcher like this enough:
#!/bin/sh
export VALGRIND_LAUNCHER=callgrind
exec /usr/local/lib/valgrind/callgrind $*
Or is there another issue that a binary package of an external tool
would have to depend on a valgrind installation?
What about vg_preload_core.so?
> I don't know why you get a segmentation fault when you run a tool
> directly - that used to work, and was a useful way of debugging the
> tools but Julian disabled it when he added the stuff to pass through
> the launcher name for client execs.
Ah, ok. I thought there might be some "magic" here.
I just tried, and it works now:
~> VALGRIND_LAUNCHER= /usr/local/lib/valgrind/memcheck ls
==414== Memcheck, a memory error detector.
...
Josef
|