setting the cache timeout for my table to -1 cause segmentation fault

I use the "mib2c.table_data.conf" as a template for my table.
Run the following command.
env MIBS="+MTYPE-MIB" mib2c -c mib2c.table_data.conf -S cache=1 mtypeTable

If "timeout" value set to any positive value and table read periodically -
everything works well.
But after I set the timeout for my table to value -1 (intend to access data
only upon request) I got segmentation fault during the request performing.
The segmentation fault happen within myTable_handler() routine. The reason
is that the table_entry pointer is out of range.
My cache flag set to :

 cache->flags |=  (
         NETSNMP_CACHE_DONT_FREE_EXPIRED  |
         NETSNMP_CACHE_PRELOAD |
         NETSNMP_CACHE_AUTO_RELOAD    );

I don't modify the cache->flags fields after initialization.
Did somebody encounter such problem?

------------------------------------------------------------------------------
WhatsUp Gold - Download Free Network Management Software
The most intuitive, comprehensive, and cost-effective network 
management toolset available today.  Delivers lowest initial 
acquisition cost and overall TCO of any competing solution.
http://p.sf.net/sfu/whatsupgold-sd

_______________________________________________
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