5.6.7. Debuggability

5.6.7.1. [Minor] Receiving large sequence numbers caused DataReader to incorrectly report on_sample_lost() with a negative total_count

When receiving any message that triggered a DataReader to report lost samples (for example, when the DataReader has BEST_EFFORT reliability and receives a sample whose sequence number is much larger than the previously received sample), the DataReader would have reported a SampleLostStatus with a negative value for the total_count if this message caused the total_count to exceed 0x7fffffff. This problem has been fixed by imposing a maximum value of 0x7fffffff for the total_count. The same problem and fix apply to total_count_change as well.

Note that RTI Issue ID CORE-8921 (which was fixed in release 6.0.0) described a more specific scenario in which the total_count could have become negative. In this release, the problem has been fixed more generally.

[RTI Issue ID CORE-14673]