hi Hallvard, I tried runnig valgrind.But summery showed me possible leak count. I was not able to co-relate the output with the actual code.
Thanks, Adarsha
On Fri, Jun 5, 2015 at 4:45 PM, Hallvard Breien Furuseth < h.b.furuseth@usit.uio.no> wrote:
On 05. juni 2015 12:31, Adarsha S wrote:
Please guide me how to identify this memory leak?
Google(find memory leaks).
Try valgrind: Try to run radiusd as "valgrind --leak-check=full radiusd ..." It'll report leaks when it exits, or you can tweak radiusd to report them once in a while when running. With a daemon you may also need to prevent it from detaching and closing stdout/stderr.
-- Hallvard