[Valgrind-developers] External tools with VG 3.1

[Josef W. <Jos...@gm...>]

Hi,

it seems that VG 3.1. comes along nicely.
In adding support for it in callgrind, there are some
changes required as tools are linked statically now:

* VG should install the needed library(ies) so that an external
tool can be statically linked.

* As was discussed when introducing the static linking, a nice
property now is that external tools can work - and thus, be
distributed - on its own. The missing thing here is the launcher.
What is the launcher doing exactly? When I run a static tool
directly, I get a SEGFAULT.
Do you think the launcher will change a lot with VG releases? If yes,
it would be good to make a library here, too. If not, I simply could
copy m_launcher.c into callgrind (to produce a "callgrind" binary),
or do you see a problem with this?

The thing here is to get binary packages for external tools which are
independent from any installed VG version / do not depend on a VG
installation at all. This would mean that you can always install the
newest valgrind nearside an older callgrind, without me being
forced to deliver a callgrind release matching the newest VG ;-)

Josef