Is your feature request related to a problem? Please describe.
On POSIX platforms with a real dynamic loader/shared object implementation, using the RTLD_GLOBAL flag to dlopen() can make it tricky or impossible to unload modules later. This flag makes the symbols globally available to satisfy other relocations, and unloading of the module will be deferred or prevented entirely as long as the runtime loader thinks a symbol is being used.

This ultimately causes a requirement failure on this platform as documented in nasa/cFE#952 - because the module isn't actually unloaded when dlclose() is called, and even though the new/replacement app module was loaded, CFE will end up restarting the original code, not the new (reloaded) code.

Loading a module with RTLD_LOCAL instead seems to prevent this issue - because the symbols are simply not made available for other modules/entities to use. This ensures that when the time comes to unload the module, nothing else is referencing the module, and dlclose() actually does unload it.

But this LOCAL flag cannot be used for all modules, because libraries do need their symbols added to the global table, or else it will not be possible to load apps that depend on those libraries

Describe the solution you'd like
Add a "flags" parameter onto the existing OS_ModuleLoad() API, so it becomes:

int32 OS_ModuleLoad(osal_id_t *module_id, const char *module_name, const char *filename, uint32 flags)

The "flags" parameter can be used to indicate the symbol visibility. A flag value of 0 should map to "global" - which is what the current implementation does - to make an easy transition for existing code.

In order to be able to look up an entry point in a module loaded with this option, this necessitates another new API:

int32 OS_ModuleSymbolLookup(osal_id_t module_id, cpuaddr *SymbolAddress, const char *SymbolName)

Which is the same as OS_SymbolLookup() but accepts a module ID value and operates on that module, rather than on the global scope. This should be the ID that was returned from the OS_ModuleLoad call.

For RTOS implementations that do not have this symbol visibility option they can ignore the flag, continue to map everything into the global symbol table as they currently do, and OS_ModuleSymbolLookup and OS_SymbolLookup become equivalent.

Additional context
Note that most all other OSAL "create" functions (tasks, queues, semaphores, etc) already have a "flags" parameter on the API, reserved for future use. Unfortunately, this flags parameter was not part of the original OS_ModuleLoad() API definition, making it an exception to the pattern. So by adding this, although it is a breaking change, it makes it more consistent with the rest of the APIs.

The alternative would be to define a separate OS_ModuleLoadWithFlags() API, but this pattern does not exist anywhere else, so it would continue to be an exception with respect to the overall OSAL API.

Requester Info
Joseph Hickey, Vantage Systems, Inc.