Re: Examine route.c! (Was: memory leak detector, 2.0.32, patch)

[Dave Wreski]

> And now, using your patch the leak seems to be in route.c line 1422:
> 
> Up 9 min:
> 24       route.c:1422
> 
> Up 11 min:
> 21277    route.c:1422

A few questions.  First, is it possible to have a baseline set of numbers
that we should expect to see, especially for buffer.c which is always
present, so non-kernel hackers can help evaulation the situation?  Just
seems like there will be plenty 'o false alarms..

Also, wasn't Purify used at one point way back when?

Dave