On Tue, 2006-02-14 at 16:51 -0500, Kyle Tucker wrote:
> Program received signal SIGSEGV, Segmentation fault.
> 0xfeeb3218 in strlen () from /usr/lib/libc.so.1
> (gdb) bt
> #0 0xfeeb3218 in strlen () from /usr/lib/libc.so.1
> #1 0xfef06520 in _doprnt () from /usr/lib/libc.so.1
> #2 0xfef08694 in vsnprintf () from /usr/lib/libc.so.1
> #3 0xff151798 in snmp_vlog (priority=7,
> format=0x7fffffff <Address 0x7fffffff out of bounds>, ap=0xff2567f0)
> at snmp_logging.c:1132
That's all? Nothing higher than 'snmp_vlog' ???
It's clear from that stack trace that the agent is choking
on the format string of some log message, but I'd expect to
see something more to indicate *what* message is being logged.
I may have to leave this for the Solaris experts. All I can
think of is some form of library mismatch. Are you using a
pre-compiled distribution, or did you build this yourself
from source?
Am I right in assuming that if you invoke this as
run -DALL -f -Le
then the agent is quite happy?
(apart from spewing out a *large* amount of debug output)
Dave
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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
