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

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

> Well, actually, no.  As far as I know only calltree does this.  For the
> most part skins like memcheck just see the client program moving values
> on/off the stack and jumping round the place, but have no concept of
> calls/returns happening.  The stack backtraces you see in error messages

Actually, I still don't understand. Despite the fact that my points of
instrumentation were meant to be function entries/exits, and as you say
this isn't necessarily the case, the code added during instrumentation is
_still_ being called multiple times despite the instrumented code only
being executed once, isn't it?

Nick