Bhaskar Bhattarai <[EMAIL PROTECTED]> wrote: > Recently I ran MemProf (Memory Profiler) against freeradius. It showed > quite a *number* of instances of memory leak (involving ip_getaddr() ).
Hmm... I ran "valgrind" against it, and didn't see any memory leak. In addition, the function in question does *not* do any memory allocation. So if there's a leak, it's in one of the functions it calls, OR one of the functions it calls allocates memory, but isn't documented as doing so. > Any solution already implemented? I don't think we need to fix anything. Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html
