memory leak in the container code

"Rasanth Akali Kandoth" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
Hi All,
Valgrind shows leak, for tables which use the mfd framework, in the
container code.
The version used is 5.3.1 .

below is the valgrind output (partial)

==3964==
==3964== 756 bytes in 21 blocks are definitely lost in loss record 117 of
163
==3964==    at 0x4005ADE: calloc (vg_replace_malloc.c:279)
==3964==    by 0x815DAEF: netsnmp_access_arp_entry_create (arp_common.c:114)
==3964==    by 0x815DE1B: _load_v4 (arp_linux.c:102)
==3964==    by 0x815DB5D: netsnmp_access_arp_container_arch_load
(arp_linux.c:27)
==3964==    by 0x815D8FA: netsnmp_access_arp_container_load
(arp_common.c:72)
==3964==    by 0x8148FF2: inetNetToMediaTable_container_load
(inetNetToMediaTable_data_access.c:265)
==3964==    by 0x8148671: _cache_load (inetNetToMediaTable_interface.c:1840)
==3964==    by 0x820AF36: _cache_load (in /usr/wichorus/snmp/sbin/snmpd)
==3964==    by 0x820AB2E: netsnmp_cache_check_and_reload (in
/usr/wichorus/snmp/sbin/snmpd)
==3964==    by 0x820ADD7: netsnmp_cache_helper_handler (in
/usr/wichorus/snmp/sbin/snmpd)
==3964==    by 0x81EB4CB: netsnmp_call_handler (agent_handler.c:428)
==3964==    by 0x81EB911: netsnmp_call_next_handler (agent_handler.c:533)
==3964==

anyone aware of any patches/fixes for the above?


-- 
Thanks&Regards,
Rasanth

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.