Closed lubowu closed 1 month ago
@lubowu We check dynamically subscribing to a topic on this test.
Would you mind sharing a reproducible example, so we can analyze whether this is a bug or a misuse of the library?
workspace_DDSHelloWorld.zip TypeLookupService.zip 1、run HelloWorld ./HelloWorld publisher 2、run TypeLookupExample ./TypeLookupExample subscriber
Have you verified this problem?
@lubowu Sorry, we haven't had time yet to check this. We'll try to find some time for it this week.
Hi @lubowu,
Sorry for the delay in the response. I could reproduce the issue. Unfortunately, the current implementation supports simple types, but we are currently working on improving that. As a result, nesting the world
struct inside the HelloWorldTopic
would be invalid.
As a workaround, I suggest doing a couple of things, first, modifying the HelloWorld.idl
(find it attached, HelloWorldMod
), then applying the patch
(also attached) that includes a correction when dealing with enums
and finally edit the HelloWorldPublisher to publish messages of type HelloWorldTopicMod
instead. Check if that overcomes the issue.
I am facing the same issue , and my backtrace on gdb is the exact same for FastDDS 2.13.2 Has there been a resolution for this yet ? @Mario-DL
Hi @lubowu @bshantam97 , Fast DDS v3.0.0 has been released. It includes Dynamic Types refactor that may have fixed the described issue. Could you check if the problem persists?
As the Dynamic Types refactor has been already introduced in the latest Fast DDS v3.0.0, we internally agreed to close all Dynamic-Types related issues. We elaborated a Migration guide to help with the upgrade process to this new major release.
Please, feel free to reopen it if the issue persists.
Is there an already existing issue for this?
Expected behavior
publisher this idl,the typelookup Segmentation fault
Current behavior
Steps to reproduce
。。。
Fast DDS version/commit
V2.6.0
Platform/Architecture
Ubuntu Focal 20.04 amd64
Transport layer
UDPv4
Additional context
No response
XML configuration file
No response
Relevant log output
No response
Network traffic capture
No response