> > Used leak(1) in anger for the first time, > > major kudos to its author. > > Our resident genius Russ. > > Leak: can't live without it.
having been using it a bit today I'm wondering if I'm missing something. Is there an easy way to record (get at) the whole function call stack at the moment of allocation (e.g. like purify gives)? Right now I just see the immediate caller of malloc which may be a bit too limited (cumbersome to work with) at times. I've been adding 'setmalloctag(x, getcallerpc(&foo))' by hand in the source to slowly get to the caller of the caller of (the caller of ...) of malloc and could imagine there is a better way... ? Axel. - nevertheless, found+plugged the leaks :-)
