Fixing a uname bug (Apache NuttX RTOS)

A bug was identified in the Apache NuttX RTOS related to the `uname` command, which failed to display the commit hash in its output. The issue arose from the static variable `g_version`, which is supposed to hold the commit hash derived from the `CONFIG_VERSION_BUILD` during the build process. The `uname` function, which is not a kernel call but a library function, retrieves this information. While the NuttX kernel correctly displayed the commit hash, the NuttX application did not, indicating a potential corruption or misconfiguration in the application environment. The investigation revealed that each NuttX application maintains its own local copy of `g_version`, which can lead to discrepancies if not properly initialized. The debugging process involved examining the disassembly of the application and confirming that the `uname` function was indeed accessing the local version of `g_version`. The findings suggest that the issue lies in how the application handles the static variable, necessitating further investigation and potential fixes to ensure that the correct commit hash is displayed consistently across both the kernel and applications.

- A bug in Apache NuttX RTOS caused the `uname` command to omit the commit hash.

- The `uname` function is a library function, not a kernel call, leading to local copies of `g_version` in applications.

- The NuttX kernel correctly displayed the commit hash, while applications did not, indicating a potential corruption.

- Debugging involved examining the disassembly of the application to trace the handling of `g_version`.

- Further investigation is needed to ensure consistent display of the commit hash across the system.