On 9 February 2010 17:29, Hindley Nick wrote:
> Were these patches eventually fed into the next iteration of the net-snmp
> release?
Yes - they are in the current 5.5 release,
and also the upcoming 5.4.3 code.
Dave
--
ck
Cc: Net-snmp-users@lists.sourceforge.net
Subject: Re: net-snmp and solaris dynamic reconfiguration
2009/1/26 Hindley Nick :
> A few weeks ago I noticed that I had a problem with snmpd core dumping.
> which is caused by an attempt to dereference cpu2 which is NULL
>
>
@lists.sourceforge.net
Subject: Re: net-snmp and solaris dynamic reconfiguration
2009/1/26 Hindley Nick :
> A few weeks ago I noticed that I had a problem with snmpd core
dumping.
> which is caused by an attempt to dereference cpu2 which is NULL
>
> (gdb) print cpu2
> $1 = (netsnmp_cpu_info *)
2009/2/2 Hindley Nick :
> I think that the fix worked. However, I got another core dump.
>
> #0 0x000796bc in var_hrproc ()
>at host/hr_proc.c:183
> 183 long_return = 100 - long_return;
> (gdb) p cpu->total_ticks
> $3 = 1092197669
> (gdb) p cpu->history[0].total_hist
> $4 =
-Original Message-
From: dave.shi...@googlemail.com [mailto:dave.shi...@googlemail.com] On
Behalf Of Dave Shield
Sent: 27 January 2009 11:15
To: Hindley Nick
Cc: Net-snmp-users@lists.sourceforge.net
Subject: Re: net-snmp and solaris dynamic reconfiguration
2009/1/26 Hindley Nick :
> A few w
2009/1/26 Hindley Nick :
> A few weeks ago I noticed that I had a problem with snmpd core dumping.
> which is caused by an attempt to dereference cpu2 which is NULL
>
> (gdb) print cpu2
> $1 = (netsnmp_cpu_info *) 0x0
> Now what I think has happened, is that the cpu... structures have been
>
hello all
A few weeks ago I noticed that I had a problem with snmpd core dumping.
My environment is as follows:
net-snmp-5.4.2.1
build options
solaris 10 SunOS xx 5.10 Generic_127111-11 sun4v sparc
SUNW,SPARC-Enterprise-T5220
when I examine the core,
(gdb) bt
#0 netsnmp_cpu_arch_load (c
