On 10/31/06, Brian Utterback <brian.utterback at sun.com> wrote: > I already know where the leaked buffer is allocated. I am trying > to track down where it is leaked. If I could see the addresses of the > unleaked buffers, I could tell if every newly allocated buffer is > immediately leaked, or if the five unleaked buffers are changing, then > they are leaking after they are used. That is, I am trying to > trace the code path of the leak, and it is not immediately > obvious, so I am looking for clues as to which path is the > culprit.
bufctl_addr::walk leakbuf will walk all of the addresses grouped into the line of output with "bufctl_addr" in it. You can use any address reported in the third column (i.e. vmem_seg or bufctl). If you want the bufctl structure instead of the allocation address, do: bufctl_addr::walk leak Cheers, - jonathan
