-
net-snmp-5.4.1.1
alpha amd64 ~arm hppa ia64 ~mips ppc ppc64 ~s390 ~sh sparc x86
diskio doc elf ipv6 lm_sensors mfd-rewrites minimal perl python rpm selinux smux ssl tcpd X sendmail extensible
View 
Download License: as-is BSD
-
net-snmp-5.4.1-r4
~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~x86
diskio doc elf ipv6 lm_sensors mfd-rewrites minimal perl python rpm selinux smux ssl tcpd X sendmail extensible
View Download License: as-is BSD
-
net-snmp-5.4.1-r3
alpha ~amd64 ~arm ~hppa ia64 ~mips ~ppc ppc64 ~s390 ~sh sparc x86
diskio doc elf ipv6 lm_sensors mfd-rewrites minimal perl python rpm selinux smux ssl tcpd X sendmail extensible
View Download License: as-is BSD
-
net-snmp-5.4.1-r1
alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86
diskio doc elf ipv6 lm_sensors mfd-rewrites minimal perl python rpm selinux smux ssl tcpd X sendmail
View Download License: as-is BSD
-
net-snmp-5.4
alpha amd64 arm hppa ia64 ~mips ppc ppc64 s390 sh sparc x86
diskio doc elf ipv6 lm_sensors mfd-rewrites minimal perl rpm selinux smux ssl tcpd X sendmail
View Download License: as-is BSD
net-snmp claims to have fixed this bug in a current build. Can the package be updated or at least marked as unstable?
(Valgrind example):
==23482== 20 bytes in 1 blocks are definitely lost in loss record 5 of 16
==23482== at 0x4A1FB80: malloc (in /usr/lib64/valgrind/amd64-linux/vgpreload_memcheck.so)
==23482== by 0x4DEFEEA: netsnmp_udp_transport (in /usr/lib64/libnetsnmp.so.15.0.0)
==23482== by 0x4DF03E9: netsnmp_udp_create_tstring (in /usr/lib64/libnetsnmp.so.15.0.0)
==23482== by 0x4DED1C4: netsnmp_tdomain_transport_full (in /usr/lib64/libnetsnmp.so.15.0.0)
==23482== by 0x4DCDFA6: snmp_sess_open (in /usr/lib64/libnetsnmp.so.15.0.0)
From this site:
www.mail-archive.com/net-snmp-coders@lists.sourceforge.net/msg09641.html
----
This is a bug. It is already fixed in revision 15683.
/MF
----
Thanks,
Doug