What is the situation that we get "netsnmp_assert 1 == new_val->high failed"?

Tatsuki Kadomoto <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <BN6PR08MB26587155C30E23312CA6ED2393600@BN6PR08MB2658.namprd08.prod.outlook.com>
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

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most 
engaging tech sites, SlashDot.org! http://sdm.link/slashdot

_______________________________________________
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
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.