zhanxiaoqi 29114efb41 sched/misc: Optimize thread saving order in coredump for easier gdb debug ... When GDB opens a coredump file, it first selects a "current thread", and the bt command by default only performs backtracing on this current thread. When there is no dedicated "crash thread marker" for this current thread in NuttX's coredump.elf, it usually degenerates to "the first thread parsed in the core file". Signed-off-by: zhanxiaoqi <zhanxiaoqi@bytedance.com>		2026-04-14 19:33:14 +08:00
..
assert.c	include/debug.h: Move to include/nuttx/debug.h	2026-04-07 07:50:06 -03:00
CMakeLists.txt
coredump.c	sched/misc: Optimize thread saving order in coredump for easier gdb debug	2026-04-14 19:33:14 +08:00
coredump.h
deadlock.c	Clean up the nxmutex library	2025-05-08 16:00:05 +08:00
Make.defs
panic_notifier.c	spinlock: Fix compilation error with atomic.h.	2025-06-25 22:13:00 +08:00
reboot_notifier.c	userspace: Exclude nuttx/arch.h	2024-11-01 16:59:37 +08:00