Re: [Valgrind-developers] (Skin writing) Linker interference with detection of function calls?

[Nicholas S. <nic...@cs...>]

>
> Josef Wiedendorfer is the real guru here as I think kcachegrind/calltree
> manages to track calls/returns.  I'm sure he can elaborate.
>

Ah. He's the one who originally suggested to me that it might be a linkage
gotcha. I'd been digging through the calltree code to try and find out how
it deals with this, but I've had little success groking it so far.

> Having said all that ... what is it you are trying to achieve with
> your skin?

Our tool (www.cse.unsw.edu.au/~drt) currently uses compile-time
instrumentation to gain call traces of programs, but this is a pain for us
and users of the tools. Since valgrind wouldn't require compile-time hacks
or a recompile, allows basic block instrumentation and seems to have been
successfully used on a number of nontrivial programs, my supervisor
thought that it would be a good idea to see if we could use it for our
instrumentation instead.

I've had a go at using dyninst for this (www.dyninst.org), but it's very
experimental and we had limited success getting it to compile and run on
our various systems (Various versions of Redhat and Debian).


Cheers,

Nick