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/CMakeLists.txt

37 lines
484 B
CMake
Raw Normal View History

license: cleanup: add SPDX Apache-2.0 license identifier Update the files which contain no license information with the 'Apache-2.0' SPDX license identifier. Many source files in the tree are missing licensing information, which makes it harder for compliance tools to determine the correct license. By default all files without license information are under the default license of Zephyr, which is Apache version 2. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2019-04-06 21:08:09 +08:00
# SPDX-License-Identifier: Apache-2.0
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-10-27 21:43:34 +08:00
zephyr_sources_ifdef(
debug: Move away from openocd and make it generic The exported structures that were originally introduced for OpenOCD have since then been reused for other debugger plugins, including PyOCD and Segger J-Link. Rename the Kconfig option and the implementation from openocd to debug thread info, so that it reflects the fact that this is no longer specifically tied to OpenOCD. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2021-03-12 02:51:35 +08:00
CONFIG_DEBUG_THREAD_INFO
thread_info.c
Introduce cmake-based rewrite of KBuild Introducing CMake is an important step in a larger effort to make Zephyr easy to use for application developers working on different platforms with different development environment needs. Simplified, this change retains Kconfig as-is, and replaces all Makefiles with CMakeLists.txt. The DSL-like Make language that KBuild offers is replaced by a set of CMake extentions. These extentions have either provided simple one-to-one translations of KBuild features or introduced new concepts that replace KBuild concepts. This is a breaking change for existing test infrastructure and build scripts that are maintained out-of-tree. But for FW itself, no porting should be necessary. For users that just want to continue their work with minimal disruption the following should suffice: Install CMake 3.8.2+ Port any out-of-tree Makefiles to CMake. Learn the absolute minimum about the new command line interface: $ cd samples/hello_world $ mkdir build && cd build $ cmake -DBOARD=nrf52_pca10040 .. $ cd build $ make PR: zephyrproject-rtos#4692 docs: http://docs.zephyrproject.org/getting_started/getting_started.html Signed-off-by: Sebastian Boe <sebastian.boe@nordicsemi.no>
2017-10-27 21:43:34 +08:00
)
systemview: add support natively using tracing hooks Add needed hooks as a subsystem that can be enabled in any application. Signed-off-by: Anas Nashif <anas.nashif@intel.com>
2018-04-06 09:06:33 +08:00
debug: Disable "at exit" LSAN leak check Disable "at exit" memory leak check by LSAN if building for a 64-bit target with GCC. This is need to fix a potential deadlock in GCCs libasan implementation. Fixes #20122 Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2019-10-27 21:50:25 +08:00
zephyr_sources_ifdef(
CONFIG_ASAN
debug: asan: Added leak suppression for SDL2 & X11 Added leak suppression, by implementing __lsan_default_suppressions function, for SDL2 and X11 library which are used by the SDL display driver. Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2019-11-03 20:39:33 +08:00
asan_hacks.c
debug: Disable "at exit" LSAN leak check Disable "at exit" memory leak check by LSAN if building for a 64-bit target with GCC. This is need to fix a potential deadlock in GCCs libasan implementation. Fixes #20122 Signed-off-by: Jan Van Winkel <jan.van_winkel@dxplore.eu>
2019-10-27 21:50:25 +08:00
)
debug: thread_analyzer: Implement thread analyzer Thread analyzer is simple module that helps in printing thread information, like stacks usage statistics. Signed-off-by: Radoslaw Koppel <radoslaw.koppel@nordicsemi.no> Signed-off-by: Bartosz Gentkowski <bartosz.gentkowski@nordicsemi.no> Signed-off-by: Joakim Andersson <joakim.andersson@nordicsemi.no>
2020-03-04 22:08:44 +08:00
zephyr_sources_ifdef(
CONFIG_THREAD_ANALYZER
thread_analyzer.c
)
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
add_subdirectory_ifdef(
CONFIG_DEBUG_COREDUMP
coredump
)
debug: x86: Add gdbstub for X86 It implements gdb remote protocol to talk with a host gdb during the debug session. The implementation is divided in three layers: 1 - The top layer that is responsible for the gdb remote protocol. 2 - An architecture specific layer responsible to write/read registers, set breakpoints, handle exceptions, ... 3 - A transport layer to be used to communicate with the host The communication with GDB in the host is synchronous and the systems stops execution waiting for instructions and return its execution after a "continue" or "step" command. The protocol has an exception that is when the host sends a packet to cause an interruption, usually triggered by a Ctrl-C. This implementation ignores this instruction though. This initial work supports only X86 using uart as backend. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
2020-05-22 07:55:28 +08:00
subsys/debug: relocate gdbstub stuff into its folder Move the gdbstub files into the gdbstub folder, and relocated its Kconfig as well. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-30 23:44:04 +08:00
add_subdirectory_ifdef(
debug: x86: Add gdbstub for X86 It implements gdb remote protocol to talk with a host gdb during the debug session. The implementation is divided in three layers: 1 - The top layer that is responsible for the gdb remote protocol. 2 - An architecture specific layer responsible to write/read registers, set breakpoints, handle exceptions, ... 3 - A transport layer to be used to communicate with the host The communication with GDB in the host is synchronous and the systems stops execution waiting for instructions and return its execution after a "continue" or "step" command. The protocol has an exception that is when the host sends a packet to cause an interruption, usually triggered by a Ctrl-C. This implementation ignores this instruction though. This initial work supports only X86 using uart as backend. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
2020-05-22 07:55:28 +08:00
CONFIG_GDBSTUB
subsys/debug: relocate gdbstub stuff into its folder Move the gdbstub files into the gdbstub folder, and relocated its Kconfig as well. Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-30 23:44:04 +08:00
gdbstub
debug: x86: Add gdbstub for X86 It implements gdb remote protocol to talk with a host gdb during the debug session. The implementation is divided in three layers: 1 - The top layer that is responsible for the gdb remote protocol. 2 - An architecture specific layer responsible to write/read registers, set breakpoints, handle exceptions, ... 3 - A transport layer to be used to communicate with the host The communication with GDB in the host is synchronous and the systems stops execution waiting for instructions and return its execution after a "continue" or "step" command. The protocol has an exception that is when the host sends a packet to cause an interruption, usually triggered by a Ctrl-C. This implementation ignores this instruction though. This initial work supports only X86 using uart as backend. Signed-off-by: Flavio Ceolin <flavio.ceolin@intel.com>
2020-05-22 07:55:28 +08:00
)
debug: Add MIPI STPv2 data stream decoder Add a decoder of STPv2 stream. Signed-off-by: Krzysztof Chruściński <krzysztof.chruscinski@nordicsemi.no>
2024-04-30 17:34:37 +08:00
zephyr_sources_ifdef(
CONFIG_MIPI_STP_DECODER
mipi_stp_decoder.c
)
debug: implement symtab generation Use pyelftools to extract the symbol table from the link stage executable. Then, filter out the function names and sort them based on their offsets before writing into the `symtab.c`, this is similar to how the `isr_tables` works. To access the structure, simply include the new header: ```c #include <zephyr/debug/symtab.h> ``` Signed-off-by: Yong Cong Sin <ycsin@meta.com>
2024-05-18 16:45:44 +08:00
add_subdirectory_ifdef(
CONFIG_SYMTAB
symtab
)