Fix #637, fix OS_ModuleUnload for static modules #638
Merged
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.
Describe the contribution
Ensure that the handle is not NULL before invoking
dlclose()
. In particular the handle will be NULL for static modules.Fixes #637
Testing performed
Build and sanity test CFE with apps linked statically.
Expected behavior changes
System(s) tested on
Ubuntu 20.04
i686-rtems4.11 / pc686 via QEMU
Additional context
This issue only affects statically linked apps, which "go through the motions" of module loading for consistency in operation, but do not actually load a module - because its already linked.
Contributor Info - All information REQUIRED for consideration of pull request
Joseph Hickey, Vantage Systems, Inc.