Re: [Valgrind-developers] sparrow

[Nick <ni...@sa...>]

Thanks a million - this is a great help. Even if it's not entirely robust, I can start investigating how we need to modify the rest of our application to accept data from valgrind now.

> 
> Unfortunately, it falls over sometimes.  The reason is, I maintain a stack
> of activation records, and if the function returned from doesn't match
> that on the top, it dies.  Actually, I do some fiddling with %esp which
> catches many uses of longjmp, but not all.

What would you call "sometimes", as a short test case?

> 
> Generally, this function entry/exit tracking is a total pain, much harder
> than you'd expect.  Anyway, it might be useful for you.
> 

Definitly useful. I still have hopes of understanding calltree's method, but I'm a lot wiser to the magnitude of the problem now.

Nick