Hi,

I am testing net-snmp for memory leaks with valgrind. I am getting the
message for still reachable in loss record. I analyze the code parse.c. It
is allocating memory for tp structure and calling do_subtree recursively.

Let me know is this an issue.

Thanks,
Jayshankar

 21,888 bytes in 114 blocks are still reachable in loss record 1,091 of
1,099
==60263==    at 0x4C2C089: calloc (vg_replace_malloc.c:760)
==60263==    by 0x63413D8: do_subtree (parse.c:1611)
==60263==    by 0x6341543: do_subtree (parse.c:1627)
==60263==    by 0x6341543: do_subtree (parse.c:1627)
==60263==    by 0x6341543: do_subtree (parse.c:1627)
==60263==    by 0x6341543: do_subtree (parse.c:1627)
==60263==    by 0x6341543: do_subtree (parse.c:1627)
==60263==    by 0x6343FF6: do_linkup (parse.c:1770)
==60263==    by 0x6343FF6: parse.constprop.7 (parse.c:4363)
==60263==    by 0x63444DB: read_module_internal (parse.c:3920)
==60263==    by 0x6342B4D: netsnmp_read_module (parse.c:4016)
==60263==    by 0x6332A6F: netsnmp_init_mib (mib.c:2657)
==60263==    by 0x63569A4: init_snmp (snmp_api.c:852)
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to