Home
last modified time | relevance | path

Searched refs:breakpoints (Results 1 – 23 of 23) sorted by relevance

/linux-4.4.14/arch/mn10300/mm/
DKconfig.cache113 icache using the cache tag registers to make breakpoints work.
122 icache using automatic purge registers to make breakpoints work.
131 tag registers to make breakpoints work.
140 purge registers to make breakpoints work.
147 invalidate the icache to make breakpoints work.
/linux-4.4.14/Documentation/powerpc/
Dptrace.txt4 4 hardware breakpoints (IAC)
23 GDB: this query will return the number of hardware breakpoints, hardware
80 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
81 that the BookE supports. COMEFROM breakpoints available in server processors
/linux-4.4.14/scripts/gdb/linux/
Dsymbols.py137 if hasattr(gdb, 'breakpoints') and not gdb.breakpoints() is None:
138 for bp in gdb.breakpoints():
/linux-4.4.14/arch/mn10300/kernel/
Dswitch_to.S81 # Lift the single-step breakpoints when the task being traced is switched out
132 # Reinstall the single-step breakpoints when the task being traced is switched
/linux-4.4.14/tools/testing/selftests/
DMakefile1 TARGETS = breakpoints
/linux-4.4.14/arch/
DKconfig106 ( These probes come in the form of single-byte breakpoints,
261 Depending on the arch implementation of hardware breakpoints,
263 breakpoints addresses, others have mixed registers to store
265 Select this option if your arch implements breakpoints under the
/linux-4.4.14/arch/m32r/platforms/oaks32r/
Ddot.gdbinit.nommu131 # Set breakpoints
/linux-4.4.14/arch/mn10300/
DKconfig.debug62 it uses temporary breakpoints to emulate single-stepping.
/linux-4.4.14/arch/m32r/platforms/m32700ut/
Ddot.gdbinit_400MHz_32MB207 # Set breakpoints
Ddot.gdbinit_200MHz_16MB207 # Set breakpoints
Ddot.gdbinit_300MHz_32MB207 # Set breakpoints
/linux-4.4.14/arch/m32r/platforms/mappi/
Ddot.gdbinit220 # Set breakpoints
Ddot.gdbinit.nommu224 # Set breakpoints
Ddot.gdbinit.smp300 # Set breakpoints
/linux-4.4.14/Documentation/frv/
Dgdbstub.txt7 port. This permits GDB to single step through the kernel, set breakpoints and
Dkernel-ABI.txt73 hardware breakpoints and watchpoints will be ignored. This mode is
/linux-4.4.14/arch/xtensa/
DKconfig201 then enter your normal kernel breakpoints once the MMU was mapped
209 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
/linux-4.4.14/Documentation/s390/
DDebugging390.txt893 If you have several breakpoints you want to put into your program &
904 script with breakpoints on every kernel procedure, this isn't a good idea
905 because there are thousands of these routines & VM can only set 255 breakpoints
1609 info breakpoints: shows all current breakpoints
1649 breakpoints
1669 info breakpoints
1670 lists all breakpoints
/linux-4.4.14/include/uapi/linux/
Dkvm.h78 struct kvm_breakpoint breakpoints[4]; member
/linux-4.4.14/Documentation/networking/
Dfilter.txt421 Sets breakpoints at particular BPF instructions. Issuing a `run` command
443 breakpoints: 0 1
444 Prints currently set breakpoints.
/linux-4.4.14/Documentation/virtual/kvm/
Dapi.txt2706 - KVM_GUESTDBG_USE_SW_BP: using software breakpoints [x86, arm64]
2707 - KVM_GUESTDBG_USE_HW_BP: using hardware breakpoints [x86, s390, arm64]
2712 For example KVM_GUESTDBG_USE_SW_BP indicates that software breakpoints
/linux-4.4.14/Documentation/virtual/uml/
DUserModeLinux-HOWTO.txt2499 session.html> , with breakpoints being set in the scheduler and in an
2786 If there's any doubt that you got the offset right, like breakpoints
/linux-4.4.14/drivers/scsi/aic7xxx/
Daic79xx.reg3396 * single step, breakpoints and program load.