OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/subsys/debug/coredump/Kconfig

72 lines
1.6 KiB
Plaintext
Raw Normal View History

debug/coredump: add a primitive coredump mechanism This adds a very primitive coredump mechanism under subsys/debug where during fatal error, register and memory content can be dumped to coredump backend. One such backend utilizing log module for output is included. Once the coredump log is converted to a binary file, it can be used with the ELF output file as inputs to an overly simplified implementation of a GDB server. This GDB server can be attached via the target remote command of GDB and will be serving register and memory content. This allows using GDB to examine stack and memory where the fatal error occurred. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-08-08 01:47:37 +08:00
# Copyright (c) 2020 Intel Corporation.
# SPDX-License-Identifier: Apache-2.0
menuconfig DEBUG_COREDUMP
kconfig: remove Enable from boolean prompts According to Kconfig guidelines, boolean prompts must not start with "Enable...". The following command has been used to automate the changes in this patch: sed -i "s/bool \"[Ee]nables\? \(\w\)/bool \"\U\1/g" **/Kconfig* Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-03-09 19:05:12 +08:00
bool "Core Dump"
debug/coredump: add a primitive coredump mechanism This adds a very primitive coredump mechanism under subsys/debug where during fatal error, register and memory content can be dumped to coredump backend. One such backend utilizing log module for output is included. Once the coredump log is converted to a binary file, it can be used with the ELF output file as inputs to an overly simplified implementation of a GDB server. This GDB server can be attached via the target remote command of GDB and will be serving register and memory content. This allows using GDB to examine stack and memory where the fatal error occurred. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-08-08 01:47:37 +08:00
depends on ARCH_SUPPORTS_COREDUMP
help
Enable core dump so it can be used for offline debugging.
if DEBUG_COREDUMP
choice
prompt "Coredump backend"
default DEBUG_COREDUMP_BACKEND_LOGGING if LOG
config DEBUG_COREDUMP_BACKEND_LOGGING
bool "Use Logging subsystem for coredump"
depends on LOG
help
Core dump is done via logging subsystem.
debug: coredump: add new backend using flash partition This adds another simple backend to use flash partition as backing storage. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-10-23 07:23:50 +08:00
config DEBUG_COREDUMP_BACKEND_FLASH_PARTITION
bool "Use flash partition for coredump"
depends on FLASH
select FLASH_MAP
select STREAM_FLASH
help
Core dump is saved to a flash partition with DTS alias
"coredump-partition".
debug: coredump: allow for coredump backends to be defined outside of tree Move coredump_backend_api struct to public header so that custom backends for coredump can be defined out of tree. Create simple backend in test directory for verification. Signed-off-by: Mark Holden <mholden@fb.com>
2022-01-08 05:02:19 +08:00
config DEBUG_COREDUMP_BACKEND_OTHER
bool "Backend subsystem for coredump defined out of tree"
help
Core dump is done via custom mechanism defined out of tree
debug/coredump: add a primitive coredump mechanism This adds a very primitive coredump mechanism under subsys/debug where during fatal error, register and memory content can be dumped to coredump backend. One such backend utilizing log module for output is included. Once the coredump log is converted to a binary file, it can be used with the ELF output file as inputs to an overly simplified implementation of a GDB server. This GDB server can be attached via the target remote command of GDB and will be serving register and memory content. This allows using GDB to examine stack and memory where the fatal error occurred. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-08-08 01:47:37 +08:00
endchoice
choice
prompt "Memory dump"
default DEBUG_COREDUMP_MEMORY_DUMP_LINKER_RAM
config DEBUG_COREDUMP_MEMORY_DUMP_MIN
bool "Minimal"
select THREAD_STACK_INFO
help
Only dumps the bare minimum memory content.
For example, the thread struct and stack of
the exception thread will be dumped.
Don't use this unless you want absolutely
minimum core dump.
config DEBUG_COREDUMP_MEMORY_DUMP_LINKER_RAM
bool "RAM defined by linker section"
help
Dumps the memory region between _image_ram_start[]
and _image_ram_end[]. This includes at least data,
noinit, and BSS sections.
This is the default.
endchoice
debug: coredump: add shell commands for logging backend This adds some shell commands to the logging backend. Since this is a simple backend, only get/clear errors are implemented. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-10-30 02:46:21 +08:00
config DEBUG_COREDUMP_SHELL
kconfig: remove Enable from boolean prompts According to Kconfig guidelines, boolean prompts must not start with "Enable...". The following command has been used to automate the changes in this patch: sed -i "s/bool \"[Ee]nables\? \(\w\)/bool \"\U\1/g" **/Kconfig* Signed-off-by: Gerard Marull-Paretas <gerard.marull@nordicsemi.no>
2022-03-09 19:05:12 +08:00
bool "Coredump shell"
debug: coredump: add shell commands for logging backend This adds some shell commands to the logging backend. Since this is a simple backend, only get/clear errors are implemented. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-10-30 02:46:21 +08:00
default y
depends on SHELL
help
This shell provides access to coredump and its backends.
debug/coredump: add a primitive coredump mechanism This adds a very primitive coredump mechanism under subsys/debug where during fatal error, register and memory content can be dumped to coredump backend. One such backend utilizing log module for output is included. Once the coredump log is converted to a binary file, it can be used with the ELF output file as inputs to an overly simplified implementation of a GDB server. This GDB server can be attached via the target remote command of GDB and will be serving register and memory content. This allows using GDB to examine stack and memory where the fatal error occurred. Signed-off-by: Daniel Leung <daniel.leung@intel.com>
2020-08-08 01:47:37 +08:00
endif # DEBUG_COREDUMP