Daniel Leung cb9f8b1019 xtensa: separate FATAL EXCEPTION printout into two ... It is observed that during logging in fatal exception, it prints "FATAL EXCEPTION(null)". Exact reason is unknown as debugging through GDB would make it all work again. So separating it into two log statements to avoid this situation. Signed-off-by: Daniel Leung <daniel.leung@intel.com>		2024-06-21 09:59:36 +02:00
..
arc
arm
arm64
common
mips
nios2
posix
riscv
sparc
x86	x86: select CONFIG_THREAD_STACK_INFO for exception stack trace	2024-06-17 21:19:32 -04:00
xtensa	xtensa: separate FATAL EXCEPTION printout into two	2024-06-21 09:59:36 +02:00
archs.yml
CMakeLists.txt
Kconfig
Kconfig.v1
Kconfig.v2