cffaa514e2
[Problem Description] In the dlmodule_load_shared_object function, if a module loading fails once due to an unresolved symbol, all subsequent attempts to load any module will fail. The system becomes unable to load modules correctly until a reboot. [Problem Analysis] The root cause is that the variable unsolved is defined as static. Static variables retain their value between function calls. If a relocation error occurs, unsolved is set to RT_TRUE. However, when the function returns with an error, the value of unsolved is not reset. Consequently, on the next function call, unsolved remains RT_TRUE from the previous execution. This causes the check if (unsolved) to trigger immediately (or after the loop), forcing the function to return an error regardless of whether the current module is valid or not. [Solution] Reset the unsolved variable to RT_FALSE before returning the error code -RT_ERROR. This ensures the variable is in a clean state for the next function call, preventing state leakage between invocations. Signed-off-by: Liu Gui <kenneth.liu@sophgo.com> |
||
|---|---|---|
| .. | ||
| dfs | ||
| drivers | ||
| fal | ||
| finsh | ||
| legacy | ||
| libc | ||
| lwp | ||
| mm | ||
| mprotect | ||
| net | ||
| rust | ||
| utilities | ||
| Kconfig | ||
| SConscript | ||