tsan warning: lock-order-inversion (potential deadlock) #14
Description
found this when running llvm thread sanitizer on my program which has control flow similar to the pubsub sample:
https://github.com/aws/aws-iot-device-sdk-cpp/blob/master/samples/PubSub/PubSub.cpp
tsan warns about this mutex sequence:
first sync_action_response_lock_ here:
https://github.com/aws/aws-iot-device-sdk-cpp/blob/master/src/ClientCoreState.cpp#L98
ack_map_lock_ here:
https://github.com/aws/aws-iot-device-sdk-cpp/blob/master/src/ClientCoreState.cpp#L197
then sync_action_response_lock_ again here:
https://github.com/aws/aws-iot-device-sdk-cpp/blob/master/src/ClientCoreState.cpp#L112
before I investigate further, is this something you've seen in testing or maybe fixed in an upcoming release?