When creating multiple clients
- one in thread A and one in thread B
- with the same unique ID
- and then receiving in thread B with
mqtt_client.try_consume_message_for(&rx_msg, 1000ms);
Causes a segmentation fault.
Yes I know that using the same unique ID twice violates the API contract.
Regardless I wanted to inform you about this issue, because there might me some deeper issue to that or at least something fragile that might cause pain points in future developments.
I use version 1.6.0
with the following flags:
-DPAHO_WITH_MQTT_C=ON
-DPAHO_BUILD_SHARED=FALSE
-DPAHO_BUILD_STATIC=TRUE
-DPAHO_WITH_SSL=TRUE
When creating multiple clients
mqtt_client.try_consume_message_for(&rx_msg, 1000ms);Causes a segmentation fault.
Yes I know that using the same unique ID twice violates the API contract.
Regardless I wanted to inform you about this issue, because there might me some deeper issue to that or at least something fragile that might cause pain points in future developments.
I use version 1.6.0
with the following flags: