RE: Table's String index does not work

2012-08-09 Thread Naama Bar Menachem
x27;s String index does not work On 9 August 2012 12:55, Naama Bar Menachem wrote: > I have also noticed that the index of the next value that was brought > get's cut: > ./data/net/naamab/snmpgetnext -m ALL -M > /data/sw/snmp/snmp_mib_lnk/ -v 2

Re: Table's String index does not work

2012-08-09 Thread Dave Shield
On 9 August 2012 12:55, Naama Bar Menachem wrote: > I have also noticed that the index of the next value that was brought > get's cut: > ./data/net/naamab/snmpgetnext -m ALL -M > /data/sw/snmp/snmp_mib_lnk/ -v 2c -c private 127.0.0.1 > 1.3.6.1.4.1.37576.4.1.4.1.1.3.\"committed-switch\" > >

Re: Table's String index does not work

2012-08-09 Thread Dave Shield
On 9 August 2012 12:55, Naama Bar Menachem wrote: > Running snmpd under debugger gave the following error message: > *** glibc detected *** /usr/bin/snmpd: free(): invalid next size > (fast): 0x0001201532a0 *** > Aborted And where is this free being called from? i.e. what is the backt

Re: Table's String index does not work

2012-08-09 Thread Dave Shield
On 9 August 2012 10:17, Naama Bar Menachem wrote: > GET-NEXT also works good but CRASHES at the end: That's an interesting description of "works" :-) > ==> next call (any call) is exit with time out! If the agent has crashed, then that is to be expected. > However WALK fails due to TimeOut: