Home
last modified time | relevance | path

Searched refs:breakpoint (Results 1 – 25 of 26) sorted by relevance

12

/linux/Documentation/arch/powerpc/
H A Dptrace.rst53 Sets a hardware breakpoint or watchpoint, according to the provided structure::
90 ptrace will return an integer (handle) uniquely identifying the breakpoint or
92 request to ask for its removal. Return -ENOSPC if the requested breakpoint
97 - set a breakpoint in the first breakpoint register::
127 - set a ranged hardware breakpoint::
155 Takes an integer which identifies an existing breakpoint or watchpoint
157 corresponding breakpoint or watchpoint..
H A Ddawr-power9.rst88 PTRACE_GETHWDBGINFO) and setting the breakpoint, userspace will get an
/linux/scripts/gdb/linux/
H A Dsymbols.py68 breakpoint = None variable in LxSymbols
185 if self.breakpoint is not None:
186 self.breakpoint.delete()
187 self.breakpoint = None
188 self.breakpoint = LoadModuleBreakpoint(
/linux/arch/sh/include/asm/
H A Dtraps.h12 BUILD_TRAP_HANDLER(breakpoint);
/linux/Documentation/trace/
H A Dkprobes.rst31 routine to be invoked when the breakpoint is hit.
66 with a breakpoint instruction (e.g., int3 on i386 and x86_64).
68 When a CPU hits the breakpoint instruction, a trap occurs, the CPU's
76 but then Kprobes would have to temporarily remove the breakpoint
176 instruction instead of a breakpoint instruction at each probepoint.
182 Kprobes inserts an ordinary, breakpoint-based kprobe at the specified
215 - code to push the CPU's registers (emulating a breakpoint trap)
264 replaced with the original code (except for an int3 breakpoint in
365 Sets a breakpoint at the address kp->addr. When the breakpoint is hit, Kprobes
401 Called with p pointing to the kprobe associated with the breakpoint,
[all …]
H A Dftrace-uses.rst107 to the pt_regs structure like it would be if an breakpoint was placed
H A Dftrace.rst2954 a breakpoint at the location to be modified, sync all CPUs, modify
2955 the rest of the instruction not covered by the breakpoint. Sync
2956 all CPUs again, and then remove the breakpoint with the finished
/linux/tools/perf/bench/
H A Dbreakpoint.c42 struct breakpoint { struct
116 struct breakpoint *breakpoints; in bench_breakpoint_thread()
H A DBuild18 perf-bench-y += breakpoint.o
/linux/Documentation/dev-tools/
H A Dgdb-kernel-debugging.rst87 - Set a breakpoint on some not yet loaded module function, e.g.::
91 Make breakpoint pending on future shared library load? (y or [n]) y
99 the breakpoint hit::
/linux/kernel/debug/kdb/
H A Dkdb_cmds5 # be safe. Global breakpoint commands affect each cpu as it is booted.
/linux/Documentation/networking/
H A Dfilter.rst456 * breakpoint 0::
458 breakpoint at: l0: ldh [12]
460 * breakpoint 1::
462 breakpoint at: l1: jeq #0x800, l2, l5
468 break when a breakpoint is being hit (another `run` will continue from
469 the currently active breakpoint executing next instructions):
485 (breakpoint)
488 * breakpoint::
H A Dtproxy.rst80 https://git.breakpoint.cc/cgit/fw/tcprdr.git/
/linux/Documentation/core-api/
H A Dentry.rst24 which means that (for example) a breakpoint in the breakpoint entry code would
25 overwrite the debug registers of the initial breakpoint.
/linux/lib/
H A DKconfig.kgdb87 This will add an extra call back to kgdb for the breakpoint
113 0x0040 - allow flow control management (breakpoint, single step)
/linux/arch/sh/kernel/
H A Dhw_breakpoint.c358 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
/linux/Documentation/translations/zh_TW/dev-tools/
H A Dgdb-kernel-debugging.rst81 Make breakpoint pending on future shared library load? (y or [n]) y
/linux/Documentation/translations/zh_CN/dev-tools/
H A Dgdb-kernel-debugging.rst85 Make breakpoint pending on future shared library load? (y or [n]) y
/linux/samples/
H A DKconfig84 tristate "Build kernel hardware breakpoint examples -- loadable module only"
87 This builds kernel hardware breakpoint example modules.
/linux/Documentation/input/devices/
H A Datarikbd.rst170 equivalent cursor control keystroke(s). The ikbd provides a single breakpoint
525 ; horizontal velocity breakpoint is reached
527 ; vertical velocity breakpoint is reached
544 seconds. After the Rn breakpoint is reached, keystroke pairs are generated
545 every Vn tenths of seconds. This provides a velocity (auto-repeat) breakpoint
/linux/arch/arm/kernel/
H A Dtraps.c623 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
/linux/arch/xtensa/
H A DKconfig575 it was possible to place a software breakpoint at 'reset' and
587 was mapped gdb wouldn't remove the breakpoint on hitting it as the
/linux/tools/perf/Documentation/
H A Dperf-record.txt92 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
96 number of bytes from specified addr, which the breakpoint will cover.
/linux/Documentation/livepatch/
H A Dlivepatch.rst31 putting a breakpoint instruction instead of any instruction.
/linux/tools/arch/x86/kcpuid/
H A Dcpuid.csv665 0x80000001, 0, ecx, 26, bpext , Data access breakpoint extension

12