Issue #2641, Fixed Null Pointer in ES Application Control API test

[dmolock-NASA]

Checklist (Please check before submitting)

• I reviewed the Contributing Guide.
• I signed and emailed the appropriate Contributor License Agreement to [email protected] and copied [email protected].

Describe the contribution

Updated the ES application control functional test for the CFE_ES_ReloadApp API to use an empty string instead of using a null pointer.

Fixes #2641

Testing performed

Built and executed the functional test and verified no failures detected in cfe_test.log file.

Expected behavior changes

No impact to behavior, functional test will execute as normal.

System(s) tested on

• Hardware: PC
• OS: RedHat 8

Contributor Info - All information REQUIRED for consideration of pull request
Dwaine Molock, NASA/GSFC

[dzbaker]

CCB 6 March 2025: CFE_ES_ReloadApp() should check for NULL input as it is a public API. Change should be to function rather than unit test.

[dmolock-NASA]

This change just fixes the current ES application control API functional test and prevents it from generating a memory segmentation fault depending on the GLIBC implementation.

The checking for a NULL pointer in the ES public API is a bigger issue, it will affect more than just CFE_ES_ReloadApp() function. There should be a ticket to verify that all public APIs that receive pointers perform a NULL pointer check.