zephyr/subsys/debug
Armin Brauns cd7a6a4d55 coredump: use memmove instead of memcpy
With CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_LINKER_RAM, buffer_output() is
called on the entire RAM memory area. This includes the stack for the
coredump thread, which is where tmp_buf is stored. Eventually, it will copy
(parts of) tmp_buf into tmp_buf itself, which invokes Undefined Behaviour
in memcpy():

> The memory areas must not overlap.  Use memmove(3) if the memory areas do
> overlap.
- memcpy(3)

With picolibc, this is detected in __memcpy_chk() and causes a fault in
__chk_fail().

Signed-off-by: Armin Brauns <armin.brauns@embedded-solutions.at>
2024-08-01 16:43:41 +02:00
..
coredump coredump: use memmove instead of memcpy 2024-08-01 16:43:41 +02:00
gdbstub subsys/debug: relocate gdbstub stuff into its folder 2024-06-04 22:36:51 -04:00
symtab subsys/debug: relocate symtab Kconfig 2024-06-04 22:36:51 -04:00
asan_hacks.c
CMakeLists.txt subsys/debug: relocate gdbstub stuff into its folder 2024-06-04 22:36:51 -04:00
Kconfig debug: thread_analyzer: Option to analyze threads on each core separately 2024-07-30 18:25:40 +01:00
mipi_stp_decoder.c debug: no UNALIGNED_ACCESS_SUPPORTED for cortex M0 or M0plus 2024-06-28 12:21:18 -04:00
thread_analyzer.c debug: thread_analyzer: fix incorrect k_thread_foreach_unlocked argument 2024-08-01 12:35:45 +02:00
thread_info.c