2010/5/28 Brendan Tauras <[email protected]> > I am writing an asynchronous polling application and testing it for > memory leaks with valgrind. I got valgrind errors regarding system > call parameters pointing to uninitiailzed data on the stack (but the > program runs as expected). > > Then I ran the simple asynchronous application tutorial code ( > http://www.net-snmp.org/wiki/index.php/TUT:Simple_Async_Application ) > with valgrind and found the same issues (but the program runs as > expected). I modified all hosts[i].name to "localhost" in the code so > I could query my local host's configured snmpd. > > I attached the valgrind output with meaningful backtraces (see the > error summary section). Could you please explain this issue and what > I should do to correct it? > > I would also like to enable more debugging; what debugging symbols > would you recommend? How would you recommend defining _DBG_IF_ and > ensuring NETSNMP_NO_DEBUGGING is undefined? >
Have you already tried to memset() the data structures passed to sendmsg() before these get initialized ? Such reports are typically caused by uninitialized padding bytes. Bart.
------------------------------------------------------------------------------
_______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
