GUIDINGLI

@pkarashchenko @masayuki2009 Let's build & run the board which really needed: https://github.com/apache/nuttx/pull/14007

@anchao @acassis **Patch Motivation & Proper Solution:** The main purpose of this patch is to address use-after-free issues that can occur when a thread unexpectedly exits. For example, in scenarios...

@acassis @hartmannathan Thanks for feeding back. We will re-test the performance data, not only osperf, but also rtos-benchmark. Also provide the flash data.

@anchao Thank you for providing some measurement data. As I mentioned before, I did not claim that this patch has no performance overhead—any robustness improvement may introduce some performance regression....

> @GUIDINGLI please fix: > > ``` > ../nuttx/tools/checkpatch.sh -c -u -m -g fc0647491b8bfaf90419ac7cb66ac6858a6cd76c..HEAD > ❌ Missing git commit message > ❌ Missing git commit message > ``` done

These three patch are will test and described on commit msg. libs/risc-v:add cfi for optimized compilation func (gdb) bt at /home/mi/ssd/dev-system/nuttx/include/string.h:321 ppcmd=, vtbl=0x80069498) at nsh_parse.c:1909 param=0x800692b8) at nsh_parse.c:2593 cmdline=cmdline@entry=0x80069750 "hello")...

@anchao Please see this reproduce testcase. If you don't have any questions about the issue, we will revert the following PR: https://github.com/apache/nuttx/pull/11832

@anchao Why close this issue before your patch merged ?