While investigating a recent problem report on a 64 bit issue, I discovered
that the function snmp_set_var_value() doesn't really do much error checking on
the values passed to it. On the other hand, snmp_varlist_add_variable() does
fairly extensive error checking, including dealing with integers that are a
different size than longs (eg some 64 bit systems).
The old_api wrapper uses snmp_set_var_value, and thus some handlers were using
a 4 byte value, which the asn build routines would choke on.
So I have a patch that basically moved the extra checking into
snmp_set_var_value(), and updates snmp_varlist_add_variable to use
snmp_set_var_value().
Any objections?
--
NOTE: messages sent directly to me, instead of the lists, will be deleted
unless they are requests for paid consulting services.
Robert Story; NET-SNMP Junkie
Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp>
Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-coders>
You are lost in a twisty maze of little standards, all different.
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
