Replies: 1 comment
-
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. 🤖💙 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
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.
Beta Was this translation helpful? Give feedback.
All reactions