zara/zephyr - zephyr - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Félix Turgeon	9cdb07cb52	scripts: coredump: Fix loading coredumps when thread info is enabled. When loading a coredump with an an elf built using 'CONFIG_DEBUG_THREAD_INFO=y', gdbstubs assumes that the thread info memoryblock populated by 'CONFIG_DEBUG_COREDUMP_MEMORY_DUMP_THREADS=y' will be present in the coredump. This is not always true and causes an error, and a failure to load the coredump. Add a default value for the threads_metadata variable in CoredumpLogFile which can be used to detect when the memory block is not present. This allows the coredump to load successfully. Signed-off-by: Félix Turgeon <felixturgeon@meta.com>	7 months ago
Mark Holden	0b9b33c540	coredump: Enable understanding of threads in scripts Update zephyr gdb-server scripts to understand threads. Parse the kernel_thread_info out of the elf file to be used for finding offsets to data from _kernel structs or from individual threads. Update log_parser to understand latest format change, which allows for the presence of a new section, threads metadata. Update gdbstub to respond to various packets to describe the threads present in a dump, and allow switching to thread context of each thread. Signed-off-by: Mark Holden <mholden@meta.com>	11 months ago
Mark Holden	d04ab82943	coredump: adjust mem_region find in gdbstub Adjust get_mem_region to not return region when address == end as there will be nothing to read there. Also, a subsequent region may have that address as a start address and would be a more appropriate selection. Signed-off-by: Mark Holden <mholden@fb.com>	3 years ago
Daniel Leung	1387e7c7c2	scripts: coredump: fix crashing on non-existent memory region get_mem_region() may return None for a non-existent memory region so we need to check first before looking at its properties. Signed-off-by: Daniel Leung <daniel.leung@intel.com>	5 years ago
Daniel Leung	49206a86ff	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>	5 years ago