On Thu, Aug 6, 2009 at 12:02 PM, [email protected]<[email protected]> wrote: > The 1 remaining valgrind error (reproduced at the end in full) is > complaining about > > "socketcall.sendmsg(msg.msg_control) points to uninitialised byte(s)".
Try to insert the statements "memset(&cmsg, 0, sizeof(cmsg)); memset(&m, 0, sizeof(m));" just after the declaration of cmsg and m and before the initialization of these structures starts. If this makes the above message disappear, please post this change as a patch on the Net-SNMP patch tracker. The above Valgrind complaint is most likely caused by uninitialized padding bytes. This is harmless but it is reported by Valgrind anyway because Valgrind doesn't know which bytes are padding bytes and which ones are not. > Any opinions of whether this error could be causing my glibc double free > errors, or whether it is a red-herring? It is unlikely that the above message printed by Valgrind is related to the double free reported by glibc. Try to trigger as much code as you can in your application and in Net-SNMP and see whether this makes Valgrind report more errors. Bart. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
