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

7 lines
215 B
Makefile
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
ccflags-y +=-I$(srctree)/include/misc/debug
CFLAGS_gdb_server.o =-I$(srctree)/include/drivers
debug: add safe memory access routines Introduces the following routines to provide safe access to memory: _mem_probe() _mem_safe_read() _mem_safe_write() _mem_safe_write_to_text_section() Those routines will return an error if the memory is not accessible rather than potentially crash. This implementation is based on the image's boundaries; thus it allows read/write access to the data/bss/init sections and read access only to the text/rodata sections. All other memory is considered invalid, even if addressable. This includes the leftover from the RAM at the end of the image, since there is no support for using it (e.g. there is no dynamic allocator). Change-Id: I6093688ecfd9b00d61be0fd453ada7bb8915c897 Signed-off-by: Benjamin Walsh <benjamin.walsh@windriver.com>
2015-09-19 03:13:17 +08:00
obj-y =
obj-$(CONFIG_MEM_SAFE_CHECK_BOUNDARIES) += mem_safe_check_boundaries.o
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
obj-$(CONFIG_GDB_SERVER) += gdb_server.o