| /linux-4.4.14/scripts/gdb/linux/ |
| D | symbols.py | 68 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-4.4.14/Documentation/powerpc/ |
| D | ptrace.txt | 47 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-4.4.14/arch/mn10300/kernel/ |
| D | switch_to.S | 95 # Remove first breakpoint
109 # Remove second breakpoint
141 # Reinstall first breakpoint
156 # Reinstall second breakpoint
|
| /linux-4.4.14/arch/cris/arch-v10/kernel/ |
| D | irq.c | 24 extern void breakpoint(void);
233 breakpoint(); in init_IRQ()
|
| D | kgdb.c | 254 void breakpoint (void); /* called by init/main.c */
1107 breakpoint(void) in breakpoint() function
|
| D | entry.S | 417 ;; special handlers for breakpoint and NMI
|
| /linux-4.4.14/arch/sh/include/asm/ |
| D | traps.h | 15 BUILD_TRAP_HANDLER(breakpoint);
|
| /linux-4.4.14/samples/ |
| D | Kconfig | 36 tristate "Build kernel hardware breakpoint examples -- loadable module only"
39 This builds kernel hardware breakpoint example modules.
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | kgdb.xml.db | 2 API-kgdb-breakpoint
|
| /linux-4.4.14/Documentation/virtual/kvm/ |
| D | s390-diag.txt | 76 DIAGNOSE function code 'X'501 - KVM breakpoint
79 If the function code specifies 0x501, breakpoint functions may be performed.
|
| D | api.txt | 2713 are enabled in memory so we need to ensure breakpoint exceptions are
2714 correctly trapped and the KVM run loop exits at the breakpoint and not
|
| /linux-4.4.14/kernel/debug/kdb/ |
| D | kdb_cmds | 5 # be safe. Global breakpoint commands affect each cpu as it is booted.
|
| /linux-4.4.14/Documentation/ |
| D | gdb-kernel-debugging.txt | 75 o Set a breakpoint on some not yet loaded module function, e.g.:
78 Make breakpoint pending on future shared library load? (y or [n]) y
85 the breakpoint hit:
|
| D | kprobes.txt | 26 routine to be invoked when the breakpoint is hit.
60 with a breakpoint instruction (e.g., int3 on i386 and x86_64).
62 When a CPU hits the breakpoint instruction, a trap occurs, the CPU's
70 but then Kprobes would have to temporarily remove the breakpoint
173 instruction instead of a breakpoint instruction at each probepoint.
178 Kprobes inserts an ordinary, breakpoint-based kprobe at the specified
208 - code to push the CPU's registers (emulating a breakpoint trap)
253 replaced with the original code (except for an int3 breakpoint in
338 Sets a breakpoint at the address kp->addr. When the breakpoint is
375 Called with p pointing to the kprobe associated with the breakpoint,
[all …]
|
| /linux-4.4.14/lib/ |
| D | Kconfig.kgdb | 66 This will add an extra call back to kgdb for the breakpoint
92 0x0040 - allow flow control management (breakpoint, single step)
|
| /linux-4.4.14/arch/cris/arch-v32/kernel/ |
| D | irq.c | 91 extern void breakpoint(void);
517 breakpoint(); in init_IRQ()
|
| D | kgdb.c | 422 void breakpoint(void);
1585 breakpoint(void) in breakpoint() function
|
| /linux-4.4.14/arch/mn10300/ |
| D | Kconfig.debug | 103 bool "Debug GDB stub breakpoint management"
107 breakpoint management.
|
| /linux-4.4.14/Documentation/frv/ |
| D | gdbstub.txt | 121 (*) Setting a software breakpoint. This sets a break instruction at the
124 (*) Setting a hardware breakpoint. The GDB stub is capable of using the IBAR
|
| /linux-4.4.14/arch/sh/kernel/ |
| D | hw_breakpoint.c | 371 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
|
| D | ptrace_64.c | 559 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
|
| /linux-4.4.14/Documentation/input/ |
| D | atarikbd.txt | 148 equivalent cursor control keystroke(s). The ikbd provides a single breakpoint
439 ; horizontal velocity breakpoint is reached
441 ; vertical velocity breakpoint is reached
458 seconds. After the Rn breakpoint is reached, keystroke pairs are generated
459 every Vn tenths of seconds. This provides a velocity (auto-repeat) breakpoint
|
| /linux-4.4.14/Documentation/networking/ |
| D | filter.txt | 416 > 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-4.4.14/arch/avr32/kernel/ |
| D | entry-avr32b.S | 837 breakpoint
860 breakpoint
|
| /linux-4.4.14/Documentation/s390/ |
| D | Debugging390.txt | 805 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-4.4.14/tools/perf/Documentation/ |
| D | perf-record.txt | 63 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
67 number of bytes from specified addr, which the breakpoint will cover.
|
| /linux-4.4.14/arch/xtensa/ |
| D | Kconfig | 200 it was possible to place a software breakpoint at 'reset' and
212 was mapped gdb wouldn't remove the breakpoint on hitting it as the
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | traps.c | 590 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
|
| /linux-4.4.14/Documentation/ia64/ |
| D | fsys.txt | 205 breakpoint that triggers at any privilege level other than 3 (user-mode).
|
| /linux-4.4.14/Documentation/trace/ |
| D | ftrace.txt | 2138 a breakpoint at the location to be modified, sync all CPUs, modify
2139 the rest of the instruction not covered by the breakpoint. Sync
2140 all CPUs again, and then remove the breakpoint with the finished
|
| /linux-4.4.14/tools/lib/traceevent/ |
| D | event-parse.c | 125 void breakpoint(void) in breakpoint() function
|
| /linux-4.4.14/drivers/scsi/aic7xxx/ |
| D | aic79xx.reg | 3519 * Sequencer instruction breakpoint address address.
|