Bart Van Assche wrote: > On Tue, Aug 4, 2009 at 4:06 PM, > [email protected]<[email protected]> wrote: >> I have an application using net-snmp 5.4.2.1 which after some time - >> seemingly proportional to the number of snmp requests - will terminate >> with a glibc double free error. The application is doing repetitive and >> simple SNMP_MSG_GET requests. After some time - could be a number of >> weeks, snmp_synch_response will return STAT_ERROR, and when >> snmp_close(ss) is called - the double free is detected after >> snmp_sess_close calls snmp_free_pdu. (full gdb output at the end). > > Did you already try to analyze the process that triggers this behavior > with Valgrind (http://www.valgrind.org/) ? > > Bart.
Hi Bart, yes - I did try to analyse the program - although it was the first time I have used valgrind, and at the time was looking for memory leaks, rather than anything else at the time. It was reporting an insignificant amount of memory lost. In hindsight I guess it is memory being freed when it shouldn't have - so maybe I need to go back and re-examine the warnings in more detail. Thanks for your reply, Craig __________ Information from ESET Smart Security, version of virus signature database 4305 (20090804) __________ The message was checked by ESET Smart Security. http://www.eset.com ------------------------------------------------------------------------------ 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
