Call stacks of all threads in zephyr

[cya0401]

Hi.

I found that there was no DEBUG_COREDUMP_MEMORY_DUMP_THREADS config before zephyr 4.0.
Does this mean that there is no way to view the call stacks of all threads in coredump before zephyr 4.0? If so, how should it be done?

For example, when I call abort() when assert is triggered actively in the program, when analyzing the coredump, I can only see the stack of abort(), but not where the real problem of the program is.

(gdb) thread apply all bt

Thread 1 (Thread <main>):
#0  eventfd_ioctl_op (obj=0x0, request=14, args=...) at zephyr/lib/posix/eventfd.c:222
#1  0x000000006159aec0 in abort () at zephyr/lib/libc/common/source/stdlib/abort.c:12
Backtrace stopped: Cannot access memory at address 0x6000004d

[github-actions]

Hi @cya0401! We appreciate you submitting your first issue for our open-source project. 🌟

Even though I'm a bot, I can assure you that the whole community is genuinely grateful for your time and effort. 🤖💙