I'm going to try the new version of netsnmp, but for now, the
5.0.8 stack trace after I do my init_agent("netsnmp") is:
(gdb) where
#0 0x0fc082b4 in pthread_mutex_lock () from /lib/libpthread.so.0
#1 0x0fa1d940 in free () from /lib/libc.so.6
#2 0x0ffdac70 in netsnmp_handler_registration_free (reginfo=0x101d9188)
at agent_handler.c:444
#3 0x0ffd4034 in netsnmp_subtree_free (a=0x101d9210)
at agent_registry.c:83
#4 0x0ffd530c in netsnmp_register_mib
(moduleName=0x101d91f8 "[EMAIL PROTECTED]", var=0x0, varsize=0,
numvars=4294967295, mibloc=0xffffdee8, mibloclen=1, priority=0,
range_subid=0, range_ubound=0, ss=0xfa1d940, context=0x0,
timeout=0, flags=0, reginfo=0x101d9188, perform_callback=262265152)
at agent_registry.c:619
#5 0x0ffda0ec in netsnmp_register_handler (reginfo=0x101d9188)
at agent_handler.c:163
#6 0x0ff003e8 in netsnmp_register_null (loc=0xffffdee8, loc_len=1)
at null.c:28
#7 0x0ffd6a90 in setup_tree () at agent_registry.c:1414
#8 0x0ffd39d4 in init_agent (app=0x1 <Address 0x1 out of bounds>)
at snmp_vars.c:231
So I understand what you said about threads not being supported by
net-snmp, but it seems to be the very last free that causes us to
seg fault. And this runs on Intel boxes. I'll let you know what
happens on 5.1pre2...
Carlos
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
