Cleanup: CorbaDispatcher: Remove find retry, unsafe initialisation of mlock #12
+6
−21
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Concurrent use of ::Instance when mlock is not initialized would create two instances of the os::Mutex, which could then potentially both be used, since the compiler does not have to expect mlock to change and may cache its current value.
Creating an os::Mutex in global scope during library init is already used in rtt/transports/mqueue/Dispatcher.hpp.