Replace KMP_INTERNAL_FREE by __kmp_free for freeing ompd_env_block #2
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.
Since ompd_env_block was allocated using __kmp_allocate(), it needs to be freed using __kmp_free(). Trying to free ompd_env_block using KMP_INTERNAL_FREE() was resulting in a crash with 'munmap_chunk(): invalid pointer'. This patch fixes this issue.
I have not checked if there are other cases where __kmp_allocate/KMP_INTERNAL_MALLOC/__kmp_free/KMP_INTERNAL_FREE have been mixed.
Also, freeing the ompd_env_block is guarded by "if (ompd_state)", while the corresponding __kmp_allocate() is not (since ompd_state gets set later). This will be fixed in a later patch.