Searched full:breakpoints (Results 1 – 25 of 28) sorted by relevance
12
| /Zephyr-latest/tests/subsys/debug/gdbstub/ |
| D | testcase.yaml | 22 debug.gdbstub.breakpoints:
46 debug.gdbstub_qemu.breakpoints:
|
| D | test_breakpoints.gdbinit | 18 # remove some of the breakpoints to check.
|
| /Zephyr-latest/doc/services/debugging/ |
| D | gdbstub.rst | 32 * Add and remove breakpoints
91 test cases ``debug.gdbstub.breakpoints`` demonstrating how the Zephyr GDB stub can be used.
297 as there are no breakpoints to further stop execution. Breaking execution
|
| /Zephyr-latest/doc/hardware/porting/ |
| D | arch.rst | 873 * If the architecture relies on interrupts to service breakpoints,
878 can continue as if no breakpoints have been encountered.
943 * Breakpoints:
948 * GDB may decide to use software breakpoints which modifies
951 restore the memory content once execution reaches the breakpoints.
953 handle software breakpoints in the architecture code (where
956 * Hardware breakpoints (type ``1``) are required if the code is
958 the architecture datasheet on how to enable hardware breakpoints.
960 * If hardware breakpoints are not supported by the architecture,
962 GDB will then rely on software breakpoints.
|
| /Zephyr-latest/boards/vcc-gnd/yd_esp32/doc/ |
| D | index.rst | 291 * When adding breakpoints, please use hardware breakpoints with command
292 ``hbreak``. Command ``break`` uses software breakpoints which requires
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wroom/doc/ |
| D | index.rst | 277 * When adding breakpoints, please use hardware breakpoints with command
278 ``hbreak``. Command ``break`` uses software breakpoints which requires
|
| /Zephyr-latest/boards/espressif/esp32_devkitc_wrover/doc/ |
| D | index.rst | 277 * When adding breakpoints, please use hardware breakpoints with command
278 ``hbreak``. Command ``break`` uses software breakpoints which requires
|
| /Zephyr-latest/boards/intel/socfpga_std/cyclonev_socdk/doc/ |
| D | index.rst | 249 Info : fpgasoc.cpu.0: hardware has 6 breakpoints, 4 watchpoints
288 Info : fpgasoc.cpu.0: hardware has 6 breakpoints, 4 watchpoints
314 Info : fpgasoc.cpu.0: hardware has 6 breakpoints, 4 watchpoints
|
| /Zephyr-latest/boards/snps/iotdk/doc/ |
| D | index.rst | 131 At this point you can do your normal debug session. Set breakpoints and then
|
| /Zephyr-latest/boards/infineon/xmc45_relax_kit/doc/ |
| D | index.rst | 106 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-latest/boards/infineon/xmc47_relax_kit/doc/ |
| D | index.rst | 108 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-latest/arch/sparc/core/ |
| D | trap_table_mvt.S | 156 SOFT_TRAP; ! 1 Breakpoints
|
| /Zephyr-latest/doc/develop/tools/ |
| D | clion.rst | 195 #. Place breakpoints by clicking in the left gutter next to the code lines.
|
| /Zephyr-latest/boards/infineon/cyw920829m2evk_02/doc/ |
| D | index.rst | 137 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-latest/boards/infineon/cy8ckit_062s4/doc/ |
| D | index.rst | 121 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-latest/boards/infineon/cy8cproto_062_4343w/doc/ |
| D | index.rst | 149 Once the gdb console starts after executing the west debug command, you may now set breakpoints and…
|
| /Zephyr-latest/boards/altr/max10/doc/ |
| D | index.rst | 306 …After this is done you may set breakpoints and continue execution. If you ever want to reset the C…
|
| /Zephyr-latest/doc/develop/debug/ |
| D | index.rst | 158 stopped at system startup. You may set breakpoints, step through code, etc. as
|
| /Zephyr-latest/boards/snps/em_starterkit/doc/ |
| D | index.rst | 241 At this point you can do your normal debug session. Set breakpoints and then
|
| /Zephyr-latest/boards/snps/emsdp/doc/ |
| D | index.rst | 225 At this point you can do your normal debug session. Set breakpoints and then
|
| /Zephyr-latest/boards/nxp/s32z2xxdc2/doc/ |
| D | index.rst | 227 At this point you can do your normal debug session. Set breakpoints and then
|
| /Zephyr-latest/subsys/debug/gdbstub/ |
| D | gdbstub.c | 802 * Breakpoints and Watchpoints in z_gdb_main_loop()
|
| /Zephyr-latest/doc/releases/ |
| D | release-notes-1.7.rst | 176 * ``ZEP-706`` - cannot set debug breakpoints on ARC side of Arduino 101
|
| /Zephyr-latest/doc/services/tracing/ |
| D | index.rst | 187 profiling. However, it can be quite useful for debugging in combination with breakpoints.
|
| /Zephyr-latest/boards/openisa/rv32m1_vega/doc/ |
| D | index.rst | 690 You can then set breakpoints and debug using normal GDB commands.
|
12
