You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Directly complime and the examples and they can not run.
Fast DDS version/commit
3.1.0
Platform/Architecture
Other. Please specify in Additional context section.
Transport layer
Default configuration, UDPv4 & SHM, TCPv4
Additional context
Platform: MacOS 15.2 Arm 64
thread_policy_set not supported for M series chips yet, therefore the function return 46 (KERN_NOT_SUPPORTED), then run into EPROSIMA_LOG_ERROR and stuck.
My temporary solution: if (0 != result) -> if (KERN_SUCCESS != result && result != KERN_NOT_SUPPORTED)
The KERN_NOT_SUPPORTED (46) error from thread_policy_set() is expected since this function isn’t supported on the platform. The log is meant to inform about this limitation, and aside from not setting the thread's affinity, it shouldn’t cause any issues.
Could you clarify where exactly you’re getting stuck? Is it the log itself, or something else? Any additional details would help us better understand the problem and assist you further.
If support for this platform is critical for your use case, feel free to reach out so we can explore possible solutions or adaptations.
Is there an already existing issue for this?
Expected behavior
Example can nomally run.
Current behavior
After running the example, no response.
Steps to reproduce
Directly complime and the examples and they can not run.
Fast DDS version/commit
3.1.0
Platform/Architecture
Other. Please specify in Additional context section.
Transport layer
Default configuration, UDPv4 & SHM, TCPv4
Additional context
Platform: MacOS 15.2 Arm 64
thread_policy_set
not supported for M series chips yet, therefore the function return 46 (KERN_NOT_SUPPORTED), then run into EPROSIMA_LOG_ERROR and stuck.My temporary solution:
if (0 != result)
->if (KERN_SUCCESS != result && result != KERN_NOT_SUPPORTED)
Refrences:
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response
The text was updated successfully, but these errors were encountered: