Re: Index Issue: container not get freed before another cache_load

Hi,

	In cache_free i used, CONTAINER_FREE (container); call. but that gives me 
segmentation fault.
Latter i thought, where index is being register, if that is freed may work. 
Therefor before going to loop and calling se_find_value_in_slist and 
se_add_pair_to_slist for index. i used se_clear_all_lists(); and it works for 
me. 

I am not sure what happend to the previous container, is that get free 
internally?

Thanks
Sharad Chandra


On Wednesday 10 October 2007 6:14 pm, Rasanth Akali Kandoth wrote:
> All,
> in snmplib/container_binary_array.c: netsnmp_binary_array_release() ,
>
>    binary_array_table *t = (binary_array_table*)c->container_data;
>     if (t->data != NULL) {
>         SNMP_FREE(t->data);
>     }
>     SNMP_FREE(t);
>     SNMP_FREE(c);
>
>
> is it fine to free t->data as above, since it is a void** ?
> is this causing the leak?
>
>
> Thanks&Regards,
> Rasanth
>
> On 10/9/07, Sharad Chandra <[email protected]> wrote:
> > Hi Guys,
> >
> >         snmpd is not able clear cache (container), I guess. I used mib2c
> > tool to
> > generate codes.
> > Once i run snmpwalk, I got
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.1.2 = INTEGER: 2
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.1.4 = INTEGER: 4
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.2.2 = STRING: "recorder 1188"
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.2.4 = STRING: "ntpd 6179"
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.3.2 = INTEGER: 1188
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.3.4 = INTEGER: 6179
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.4.2 = INTEGER: 2
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.4.4 = INTEGER: 2
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.5.2 = STRING: "pid (1188)|  "
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.5.4 = STRING: "pid (6179)|  "
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.6.2 = INTEGER: 1
> > SNMPv2-SMI::enterprises.5713.2.10.15.40.1.6.4 = INTEGER: 1
> >
> > check first 2 lines that is Index-ID. it should go 1,2,3,4 ...... and so
> > on.
> > initially it was 1,2 as two process are monitored
> > then i kill process 1, then indexing remains to 2,
> > I think it should shift to one. [Which can be if container gets cleaned]
> >
> > and then i run process 1 again.. now index become 2,3 instead of 1,2
> >
> > Should i must give some entry in
> > processStatusTable_cache_free(netsnmp_container *container)
> > function of "_data_access.c" generated by mib2c to free the container
> >
> > Thanks for any suggestion
> > Sharad Chandra
> >
> > -------------------------------------------------------------------------
> > 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
> > [email protected]
> > Please see the following page to unsubscribe or change other options:
> > https://lists.sourceforge.net/lists/listinfo/net-snmp-users

-------------------------------------------------------------------------
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/