debug: coredump: handle xtensa coredump like everyone else

There should not be any special handling for coredump with xtensa.

Signed-off-by: Anas Nashif <anas.nashif@intel.com>
This commit is contained in:
Anas Nashif 2023-12-12 07:33:47 -05:00 committed by Carles Cufí
commit a7e8391e31
2 changed files with 0 additions and 6 deletions

View file

@ -9,7 +9,6 @@
#include <inttypes.h>
#include <xtensa/config/specreg.h>
#include <xtensa_backtrace.h>
#include <zephyr/debug/coredump.h>
#include <zephyr/arch/common/exc_handle.h>
#include <xtensa_internal.h>
@ -96,7 +95,6 @@ void xtensa_fatal_error(unsigned int reason, const z_arch_esf_t *esf)
xtensa_dump_stack(esf);
coredump(reason, esf, IS_ENABLED(CONFIG_MULTITHREADING) ? k_current_get() : NULL);
#if defined(CONFIG_XTENSA_ENABLE_BACKTRACE)
#if XCHAL_HAVE_WINDOWED

View file

@ -13,9 +13,7 @@
#include <zephyr/logging/log_ctrl.h>
#include <zephyr/logging/log.h>
#include <zephyr/fatal.h>
#ifndef CONFIG_XTENSA
#include <zephyr/debug/coredump.h>
#endif
LOG_MODULE_DECLARE(os, CONFIG_KERNEL_LOG_LEVEL);
@ -115,9 +113,7 @@ void z_fatal_error(unsigned int reason, const z_arch_esf_t *esf)
LOG_ERR("Current thread: %p (%s)", thread,
thread_name_get(thread));
#ifndef CONFIG_XTENSA
coredump(reason, esf, thread);
#endif
k_sys_fatal_error_handler(reason, esf);