Bart, I've had a quick look at the code for winExtDLL.c (in response to bug #2971257), and there's something that confuses (/concerns) me.
Within the var_winExtDLL handler, there's the usual (for request = requests; request; request = request->next ) loop, to work through all the relevant varbinds for this call. So far, so good. But then immediately within this block is another loop, starting from the 'requestvb' field of this first request and walking through the 'next_variable' links. That's not something which a handler should normally be concerned about - this list is really for the benefit of the main agent processing code. The handler should be working with the "requests" list, and accessing each 'request->requestvb' What is this code trying to do? I haven't looked closely through the whole of this routine, but I strongly suspect that its design is at odds with the operation of the helper mechanism. Particularly as relates to the processing of multi-varbind requests. Dave ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Net-snmp-coders mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
