On 01/08/07, Zack Little <[EMAIL PROTECTED]> wrote:
>  I've been adding trace messages trying to figure out what is happening and
> I've got a better understanding of the problem.
>
>  The code doesn't always blow up in the same spot (or function), but the
> place it blows up almost always seems to be related to a compare.

Have you got a feeling for which MIB module(s) are triggering this problem?
snmp_oid_compare is a very low-level routine, and is invoked all over the
place - we'd really need to know which OIDs are being compared, in order
to have any chance of tracking down where the problem might actually lie

Dave

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to