mirror of
https://github.com/apache/nuttx.git
synced 2026-10-04 04:38:10 +00:00
ec78241ebe
An architecture that sets CONFIG_ARCH_USE_DATA_HEAP gives a loaded module its data from up_dataheap_memalign(), because the ordinary heap is not where that data belongs there. The ELF loader honours it for every object but an FDPIC one: an FDPIC object places its writable segment on its own, and that allocation, and the two places that free it, still use lib_memalign() and lib_free(). Its text already comes from the text heap. So an FDPIC module's data goes to the data heap too, and back to it when the module is unloaded or removed. On mps3-an547, which sets both heaps, fdpicxip loaded the data of its two instances at 0x1007220 and 0x104e480, in the ordinary heap. With this change they are at 0x21000000 and 0x21000180, in the SRAM2 data heap, and both instances run. In a protected build the difference matters: there the ordinary heap is kernel memory, and the module takes a data access violation on its first access to its data. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Marco Casaroli <marco.casaroli@gmail.com> |
||
|---|---|---|
| .. | ||
| libbuiltin | ||
| libc | ||
| libdsp | ||
| libm | ||
| libnx | ||
| libxx | ||
| CMakeLists.txt | ||