zephyr/arch
Paul Sokolovsky ec1ffc8bcf arch: x86: fatal: If possible, print thread name in crash dump
It's relatively hard to figure out what thread a crash happens in
from the crash dump. E.g, it's usually not immediately possible to
find it out from linker map due to the fact that static symbols are
not there (https://sourceware.org/bugzilla/show_bug.cgi?id=16566).

So, try to do it as easy if possible, by just printing thread name
in a dump, if thread names are enabled at all.

Signed-off-by: Paul Sokolovsky <paul.sokolovsky@linaro.org>
2019-04-24 09:01:07 -07:00
..
arc arch: arc: optimize the push and pop of fast irq 2019-04-19 14:37:03 -05:00
arm arch: all: Remove not used struct _caller_saved 2019-04-18 12:24:56 -07:00
common license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
nios2 arch: all: Remove not used struct _caller_saved 2019-04-18 12:24:56 -07:00
posix arch: all: Remove not used struct _caller_saved 2019-04-18 12:24:56 -07:00
riscv32 arch: all: Remove not used struct _caller_saved 2019-04-18 12:24:56 -07:00
x86 arch: x86: fatal: If possible, print thread name in crash dump 2019-04-24 09:01:07 -07:00
x86_64 arch: all: Remove not used struct _caller_saved 2019-04-18 12:24:56 -07:00
xtensa arch: all: Remove not used struct _caller_saved 2019-04-18 12:24:56 -07:00
CMakeLists.txt license: cleanup: add SPDX Apache-2.0 license identifier 2019-04-07 08:45:22 -04:00
Kconfig userspace: set default priv stack size to 1024 2019-03-29 22:21:16 -04:00