So I did: Report #1654423 However, I would like the discussion here to continue, as I am trying to nail it down on my own. Any feedback would be appreciated.
I found out that the crash happens when, after processing all requests, the loop goes into processing extra commit requests. I am submitting 15 sets, but the loop processes 17 commits, and crashes on the 17th. Is this standard behavior? Are the extra commits needed? -----Original Message----- From: Thomas Anders [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 06, 2007 8:49 PM To: Wojciech Jawor Cc: net-snmp-coders@lists.sourceforge.net Subject: Re: how are SET requests handled? - a possible bug Wojciech Jawor wrote: > The "large" number of columns makes my agent crash on set requests. I > suspect that this is due to a bug that reveals itself when operating on > larger tables (with larger number of columns that is, and not > necessarily many rows). Can you please (also) submit this as a bug on http://www.net-snmp.org/bugs so it won't get lost? Cheers, Thomas -- Thomas Anders (thomas.anders at blue-cable.de) ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-coders mailing list Net-snmp-coders@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
