Home
last modified time | relevance | path

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

12

/Linux-v4.19/scripts/gdb/linux/
Dsymbols.py68 breakpoint = None variable in LxSymbols
166 if self.breakpoint is not None:
167 self.breakpoint.delete()
168 self.breakpoint = None
169 self.breakpoint = LoadModuleBreakpoint(
/Linux-v4.19/Documentation/powerpc/
Dptrace.txt47 Sets a hardware breakpoint or watchpoint, according to the provided structure:
84 ptrace will return an integer (handle) uniquely identifying the breakpoint or
86 request to ask for its removal. Return -ENOSPC if the requested breakpoint
91 - set a breakpoint in the first breakpoint register
121 - set a ranged hardware breakpoint
149 Takes an integer which identifies an existing breakpoint or watchpoint
151 corresponding breakpoint or watchpoint..
/Linux-v4.19/arch/sh/include/asm/
Dtraps.h16 BUILD_TRAP_HANDLER(breakpoint);
/Linux-v4.19/Documentation/virtual/kvm/
Ds390-diag.txt76 DIAGNOSE function code 'X'501 - KVM breakpoint
79 If the function code specifies 0x501, breakpoint functions may be performed.
/Linux-v4.19/Documentation/dev-tools/
Dgdb-kernel-debugging.rst83 - Set a breakpoint on some not yet loaded module function, e.g.::
87 Make breakpoint pending on future shared library load? (y or [n]) y
95 the breakpoint hit::
Dkgdb.rst559 putting a breakpoint at ``sys_sync`` and then you can run ``sync`` from a
621 breakpoint operations, because it can disrupt the state of the kernel
698 implement HW breakpoint as well as the initialization to dynamically
751 - SW / HW breakpoint management for the kdb shell
/Linux-v4.19/kernel/debug/kdb/
Dkdb_cmds5 # be safe. Global breakpoint commands affect each cpu as it is booted.
/Linux-v4.19/Documentation/
Dkprobes.txt30 routine to be invoked when the breakpoint is hit.
65 with a breakpoint instruction (e.g., int3 on i386 and x86_64).
67 When a CPU hits the breakpoint instruction, a trap occurs, the CPU's
75 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
363 Sets a breakpoint at the address kp->addr. When the breakpoint is
402 Called with p pointing to the kprobe associated with the breakpoint,
[all …]
/Linux-v4.19/samples/
DKconfig44 tristate "Build kernel hardware breakpoint examples -- loadable module only"
47 This builds kernel hardware breakpoint example modules.
/Linux-v4.19/lib/
DKconfig.kgdb66 This will add an extra call back to kgdb for the breakpoint
92 0x0040 - allow flow control management (breakpoint, single step)
/Linux-v4.19/arch/sh/kernel/
Dhw_breakpoint.c360 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
Dptrace_64.c560 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
/Linux-v4.19/Documentation/networking/
Dtproxy.txt77 https://git.breakpoint.cc/cgit/fw/tcprdr.git/
Dfilter.txt416 > breakpoint 0
417 breakpoint at: l0: ldh [12]
418 > breakpoint 1
419 breakpoint at: l1: jeq #0x800, l2, l5
423 break when a breakpoint is being hit (another `run` will continue from
424 the currently active breakpoint executing next instructions):
439 (breakpoint)
442 > breakpoint
/Linux-v4.19/Documentation/input/devices/
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-v4.19/Documentation/s390/
DDebugging390.txt805 To delete a particular breakpoint issue
806 TR DEL <breakpoint number>
830 Setting a simple breakpoint
1049 hit b to continue till breakpoint
1050 reach the breakpoint
1058 & the TR I PSWA <Driver open address> will be the only active breakpoint again.
1118 We have stopped at a breakpoint
1653 sets a breakpoint
1664 Set a breakpoint for all functions matching REGEXP
1667 will set a breakpoint with all functions with 390 in their name.
[all …]
/Linux-v4.19/drivers/scsi/hisi_sas/
Dhisi_sas.h314 struct hisi_sas_breakpoint *breakpoint; member
Dhisi_sas_main.c1987 memset(hisi_hba->breakpoint, 0, s); in hisi_sas_init_mem()
2095 hisi_hba->breakpoint = dmam_alloc_coherent(dev, s, in hisi_sas_alloc()
2098 if (!hisi_hba->breakpoint) in hisi_sas_alloc()
/Linux-v4.19/arch/arm/kernel/
Dtraps.c626 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
/Linux-v4.19/arch/xtensa/
DKconfig225 it was possible to place a software breakpoint at 'reset' and
237 was mapped gdb wouldn't remove the breakpoint on hitting it as the
/Linux-v4.19/tools/perf/Documentation/
Dperf-record.txt81 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
85 number of bytes from specified addr, which the breakpoint will cover.
/Linux-v4.19/Documentation/trace/
Dftrace-uses.rst107 to the pt_regs structure like it would be if an breakpoint was placed
/Linux-v4.19/Documentation/ia64/
Dfsys.txt205 breakpoint that triggers at any privilege level other than 3 (user-mode).
/Linux-v4.19/Documentation/livepatch/
Dlivepatch.txt44 putting a breakpoint instruction instead of any instruction.
/Linux-v4.19/kernel/trace/
DKconfig485 If kprobes can use ftrace instead of breakpoint, ftrace related

12