OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/arch/x86/core/debug/debug_frames.c

22 lines
399 B
C
Raw Normal View History

debug: add target GDB server The GDB server implements a set of GDB commands, such as read/write memory, read/write registers, connect/detach, breakpoints, single-step, continue. It is not OS-aware, and thus provides a 'system-level' debugging environment, where the system stops when debugging (such as handling a breakpoint or single-stepping). It currently only works over a serial line, taking over the uart_console. If target code prints over the console, the GDB server intecepts them and does not send the characters directly over the serial line, but rather wraps them in a packet handled by the GDB client. Change-Id: Ic4b82e81b5a575831c01af7b476767234fbf74f7 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-04-12 05:51:39 +08:00
/*
* Copyright (c) 2015 Wind River Systems, Inc.
*
license: Replace Apache boilerplate with SPDX tag Replace the existing Apache 2.0 boilerplate header with an SPDX tag throughout the zephyr code tree. This patch was generated via a script run over the master branch. Also updated doc/porting/application.rst that had a dependency on line numbers in a literal include. Manually updated subsys/logging/sys_log.c that had a malformed header in the original file. Also cleanup several cases that already had a SPDX tag and we either got a duplicate or missed updating. Jira: ZEP-1457 Change-Id: I6131a1d4ee0e58f5b938300c2d2fc77d2e69572c Signed-off-by: David B. Kinder <david.b.kinder@intel.com> Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
2017-01-19 09:01:01 +08:00
* SPDX-License-Identifier: Apache-2.0
debug: add target GDB server The GDB server implements a set of GDB commands, such as read/write memory, read/write registers, connect/detach, breakpoints, single-step, continue. It is not OS-aware, and thus provides a 'system-level' debugging environment, where the system stops when debugging (such as handling a breakpoint or single-stepping). It currently only works over a serial line, taking over the uart_console. If target code prints over the console, the GDB server intecepts them and does not send the characters directly over the serial line, but rather wraps them in a packet handled by the GDB client. Change-Id: Ic4b82e81b5a575831c01af7b476767234fbf74f7 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-04-12 05:51:39 +08:00
*/
/**
* @file
* @brief Stack frames for debugging purposes
*
* This file contains a routine useful for debugging that gets a pointer to
* the current interrupt stack frame.
*/
kernel: replace all remaining nanokernel occurances replace include <nanokernel.h> with <kernel.h> everywhere and also fix any remaining mentions of nanokernel. Keep the legacy samples/tests as is. Change-Id: Iac48447bd191e83f21a719c69dc26233216d08dc Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-12-23 21:35:34 +08:00
#include <kernel.h>
kernel/arch: consolidate tTCS and TNANO definitions There was a lot of duplication between architectures for the definition of threads and the "nanokernel" guts. These have been consolidated. Now, a common file kernel/unified/include/kernel_structs.h holds the common definitions. Architectures provide two files to complement it: kernel_arch_data.h and kernel_arch_func.h. The first one contains at least the struct _thread_arch and struct _kernel_arch data structures, as well as the struct _callee_saved and struct _caller_saved register layouts. The second file contains anything that needs what is provided by the common stuff in kernel_structs.h. Those two files are only meant to be included in kernel_structs.h in very specific locations. The thread data structure has been separated into three major parts: common struct _thread_base and struct k_thread, and arch-specific struct _thread_arch. The first and third ones are included in the second. The struct s_NANO data structure has been split into two: common struct _kernel and arch-specific struct _kernel_arch. The latter is included in the former. Offsets files have also changed: nano_offsets.h has been renamed kernel_offsets.h and is still included by the arch-specific offsets.c. Also, since the thread and kernel data structures are now made of sub-structures, offsets have to be added to make up the full offset. Some of these additions have been consolidated in shorter symbols, available from kernel/unified/include/offsets_short.h, which includes an arch-specific offsets_arch_short.h. Most of the code include offsets_short.h now instead of offsets.h. Change-Id: I084645cb7e6db8db69aeaaf162963fe157045d5a Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-11-08 23:36:50 +08:00
#include <kernel_structs.h>
debug: add target GDB server The GDB server implements a set of GDB commands, such as read/write memory, read/write registers, connect/detach, breakpoints, single-step, continue. It is not OS-aware, and thus provides a 'system-level' debugging environment, where the system stops when debugging (such as handling a breakpoint or single-stepping). It currently only works over a serial line, taking over the uart_console. If target code prints over the console, the GDB server intecepts them and does not send the characters directly over the serial line, but rather wraps them in a packet handled by the GDB client. Change-Id: Ic4b82e81b5a575831c01af7b476767234fbf74f7 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-04-12 05:51:39 +08:00
NANO_ISF *sys_debug_current_isf_get(void)
{
debug: gdb: move to new kernel APIs Change-Id: Ifed1fe7c60fa150ee3ef4fefabafeb95312bf8bc Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2016-12-18 22:12:27 +08:00
return _kernel.arch.isf;
debug: add target GDB server The GDB server implements a set of GDB commands, such as read/write memory, read/write registers, connect/detach, breakpoints, single-step, continue. It is not OS-aware, and thus provides a 'system-level' debugging environment, where the system stops when debugging (such as handling a breakpoint or single-stepping). It currently only works over a serial line, taking over the uart_console. If target code prints over the console, the GDB server intecepts them and does not send the characters directly over the serial line, but rather wraps them in a packet handled by the GDB client. Change-Id: Ic4b82e81b5a575831c01af7b476767234fbf74f7 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2016-04-12 05:51:39 +08:00
}