On 9 August 2012 12:55, Naama Bar Menachem <[email protected]> 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\" > > NOVELSAT-DEMODULATOR-MIB::nsDemodConfigDiseqcNumDataBytes."non-committed > -sw" = Gauge32: 1 > ===> when the index value should actually be "non-committed-switch"
I note from your nsDemodConfigDiseqcTable_get_next_entry() routine that you are setting the value for the index varbind manually (using 'strncpy') Is there a good reason why you aren't using the snmp_set_var_value() API to handle this? I haven't checked the details of your code, but it doesn't look as if it's dealing with the internal varbind buffer properly. Please try using the standard API for setting the index value. It wouldn't surprise me if your crash is caused by corruption of the varbind structure. Dave ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ 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
