This website requires JavaScript.
Explore
Help
Sign In
OrgZephyr
/
zephyr
mirror of
https://github.com/zephyrproject-rtos/zephyr.git
Watch
1
Star
0
Fork
You've already forked zephyr
0
Code
Issues
Releases
Wiki
Activity
7bcbd6133a
zephyr
/
arch
/
x86
/
debug
/
Makefile
3 lines
54 B
Makefile
Raw
Normal View
History
Unescape
Escape
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
x86: improve exception APIs Previously, exception stubs had to be declared in assembly language files. Now we have two new APIs to regsiter exception handlers at C toplevel: _EXCEPTION_CONNECT_CODE(handler, vector) _EXCEPTION_CONNECT_NOCODE(handler, vector) For x86 exceptions that do and do not push error codes onto the stack respectively. In addition, it's now no longer necessary to #define around exception registration. We now use .gnu.linkonce magic such that the first _EXCEPTION_CONNECT_*() that the linker finds is used for the specified vector. Applications are free to install their own exception handlers which will take precedence over default handlers such as installed by arch/x86/core/fatal.c Some Makefiles have been adjusted so that the default exception handlers in arch/x86/core/fatal.c are linked last. The code has been tested that the right order of precedence is taken for exceptions overridden in the floating point, gdb debug, or application code. The asm SYS_NANO_CPU_EXC_CONNECT API has been removed; it was ill- conceived as it only worked for exceptions that didn't push error codes. All the asm NANO_CPU_EXC_CONNECT_* APIs are gone as well in favor of the new _EXCEPTION_CONNNECT_*() APIs. CONFIG_EXCEPTION_DEBUG no longer needs to be disabled for test cases that define their own exception handlers. Issue: ZEP-203 Change-Id: I782e0143fba832d18cdf4daaa7e47820595fe041 Signed-off-by: Andrew Boie <andrew.p.boie@intel.com>
2016-07-27 05:55:41 +08:00
obj-$(CONFIG_GDB_SERVER)
=
gdb_arch.o gdb_dbg_regs.o