Do not destroy mutexes in coap_cleanup() #1226
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If mutexes are destroyed in coap_cleanup() they can never be re-initialized as calling coap_startup() short-circuits after its first invocation. This updates to not destroy the mutexes on calls to coap_cleanup(). Signed-off-by: Daniel Mangum <[email protected]>
|
If the mutexes allocate any memory in The issue you are finding here needs to be solved in another way. See some of my suggestions in #1225. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
If mutexes are destroyed in coap_cleanup() they can never be re-initialized as calling coap_startup() short-circuits after its first invocation. This updates to not destroy the mutexes on calls to coap_cleanup().
Fixes #1225