5.4.24. Other

5.4.24.1. [Critical] Data races on architectures with weak memory models

On systems with weak memory architectures, such as Arm® and PowerPC®, data races could have led to undefined behavior or crashes in various Connext components.

[RTI Issue ID CORE-15002]

5.4.24.2. [Major] Printing an IDL union with an enum discriminator could have produced an incorrect output

When printing an IDL union with an enum discriminator, the resulting case labels may have been incomplete if the enum types were defined in a separate module.

[RTI Issue ID CORE-14654]

5.4.24.3. [Major] Incorrect CPU assignment when using THREAD_SETTINGS_CPU_RR_ROTATION in receiver_pool

There was an incorrect CPU assignment for the receive threads when using the THREAD_SETTINGS_CPU_RR_ROTATION setting in the receiver_pool. Specifically, all the receive threads were assigned to the first CPU listed in the cpu_list.

[RTI Issue ID CORE-13211]

5.4.24.4. [Trivial] Possible data race when creating DomainParticipants

During the creation of a DomainParticipant, it was possible to run into a data race due to the use of the localtime or gmtime API by other threads in Connext. There was no functional impact of this data race; however, it has been fixed by using the safe versions of those APIs available on the different operating systems.

[RTI Issue ID CORE-14877]

5.4.24.5. [Trivial] Printing a type with an annotation using an enum produced an incorrect output

When printing a type with an annotation using an enum, the resulting annotations contained the ordinal instead of the enum type name.

[RTI Issue ID CORE-14729]