4.6. Debuggability

4.6.1. [Minor] polling_period was not required to be a positive value

The Core Libraries User’s Manual states that DDS_MonitoringPeriodicDistributionSettings ::polling_period must be > 0 seconds. This requirement was not enforced. If the polling_period was not a positive value, then Monitoring Library 2.0 was incorrectly allowed to be enabled.

[RTI Issue ID MONITOR-720]

4.6.2. [Minor] take_discovery_snapshot may have provided inaccurate information for remote endpoints

Using the take_discovery_snapshot APIs (for example, rti::util::discovery::take_snapshot in modern C++) could return inaccurate information for remote entities. Examples of incorrect data included:

An incorrect entity name
Incorrect partitions

[RTI Issue ID CORE-16182]

4.6.3. [Minor] Incorrect timestamp in log messages with microseconds higher than 500000

Since Connext 7.2.0, the function that printed the timestamp for log messages has been incorrectly rounding up the seconds value, if the microseconds were higher than 500000. This led to inconsistent timing in the logging showing the timestamp moving backwards:

[2026-02-11 14:27:19.951264] DEBUG rCo#########Evt
  Mx06:RTIEventActiveGeneratorThread_loop:rCo#########Evt sleeping {00000000,2F80453E}
[2026-02-11 14:27:19.136920] DEBUG rCo#########Evt
  Mx06:RTIEventActiveGeneratorThread_loop:rCoShant####Evt gathering events

This regression has been fixed, and now the timestamp is displayed properly.

[RTI Issue ID CORE-16508]

4.6.4. [Trivial] Backtraces did not correctly print addresses higher than 0xFFFFFFFF

Backtraces logged by Connext did not correctly print addresses higher than 0xFFFFFFFF. Now, Connext prints backtraces showing the right addresses.

[RTI Issue ID CORE-16517]