Tatsuki Kadomoto
2017-01-05 02:20:27 UTC
Hi,
I'm using NetSNMP 5.7.3 and encountered the following message.
"netsnmp_assert 1 == new_val->high failed int64.c:370 netsnmp_c64_check32_and_update() "
Looks like this is a bug that unwanted message is shown in the log and is already addressed in the upstream.
https://sourceforge.net/p/net-snmp/code/ci/333aea41eb8bcdb9afae6bb89f3581f8e70ee830
But what exactly does this message mean? Does it affect anything to NetSNMP users?
I have checked the comment in int64.c below but I couldn't understand.
I would appreciate if someone could explain the situation we get this message in easier words.
===
366 /*
367 * check wrap incremented high, so reset it. (Because having
368 * high set for a 32 bit counter will confuse us in the next update).
369 */
===
Regards,
Tatsuki
I'm using NetSNMP 5.7.3 and encountered the following message.
"netsnmp_assert 1 == new_val->high failed int64.c:370 netsnmp_c64_check32_and_update() "
Looks like this is a bug that unwanted message is shown in the log and is already addressed in the upstream.
https://sourceforge.net/p/net-snmp/code/ci/333aea41eb8bcdb9afae6bb89f3581f8e70ee830
But what exactly does this message mean? Does it affect anything to NetSNMP users?
I have checked the comment in int64.c below but I couldn't understand.
I would appreciate if someone could explain the situation we get this message in easier words.
===
366 /*
367 * check wrap incremented high, so reset it. (Because having
368 * high set for a 32 bit counter will confuse us in the next update).
369 */
===
Regards,
Tatsuki