Lines Matching full:breakpoint
221 breakpoint instruction, registers, and how to set up and tear down the
434 3.2 Breakpoint Handling
437 In general, a breakpoint is a user-designated location in the program
446 register into which the breakpoint address may be stored. If the PC
447 (shorthand for "program counter") ever matches a value in a breakpoint
452 processor, and force it to stop if the address matches a breakpoint's
459 do anything more than set the breakpoint and wait for something to
483 Also, the software breakpoint instruction should be the smallest
486 middle of the breakpoint instruction. (Strictly speaking, the
487 breakpoint must be no larger than the smallest interval between
491 a software breakpoint, although in practice only the ARC has failed to
494 Basic breakpoint object handling is in `breakpoint.c'. However,
495 much of the interesting breakpoint action is in `infrun.c'.
499 Insert or remove a software breakpoint at address
501 failure. On input, BP_TGT contains the address of the breakpoint,
504 information about the breakpoint on output. The field
505 `placed_address' may be updated if the breakpoint was placed at a
507 contents of the bytes where the breakpoint has been inserted, if
508 reading memory would return the breakpoint instead of the
518 remove the breakpoint.
522 Insert or remove a hardware-assisted breakpoint at address
547 in the output of the `maint info breakpoint' command.
638 `breakpoint.h' as follows:
645 hw_execute = 3 /* Execute HW breakpoint */
809 this function. This function examines the breakpoint condition
817 function examines the breakpoint condition bits in the DR6 Debug
859 instruction execution, and each hardware-assisted breakpoint
1823 as the frame ID for a given breakpoint means that the breakpoint is not
2006 breakpoint on a function). Global names and file-scope names will
3908 it is essential that if a function does hit a breakpoint, commands like
3975 on the target as its return address. A temporary breakpoint will
3977 breakpoint.
3982 breakpoint is encountered.
3991 value (the address at which the breakpoint instruction should be
4100 `BREAKPOINT'
4102 into memory where a breakpoint is set. Although it's common to
4103 use a trap instruction for a breakpoint, it's not required; for
4105 breakpoint must be no longer than the shortest instruction of the
4108 `BREAKPOINT' has been deprecated in favor of
4113 Similar to BREAKPOINT, but used for bi-endian targets.
4120 breakpoint instruction. It returns a pointer to a static string
4121 of bytes that encode a breakpoint instruction, stores the length
4124 breakpoint should be inserted. May return `NULL' to indicate that
4127 Although it is common to use a trap instruction for a breakpoint,
4129 invalid instruction. The breakpoint must be no longer than the
4132 Provided breakpoint bytes can be also used by
4135 copy if it was called for a location with permanent breakpoint as
4136 some architectures use breakpoint instructions containing
4139 Replaces all the other BREAKPOINT macros.
4153 custom breakpoint insertion and removal routines if
4158 Given an address at which a breakpoint is desired, return a
4159 breakpoint address adjusted to account for architectural
4160 constraints on breakpoint placement. This method is not needed by
4173 the bundle. So, if the user attempts to place a breakpoint on one
4182 breakpoint's address by scanning backwards for the beginning of
4185 Since the adjustment of a breakpoint may significantly alter a
4187 breakpoint is initially set and each time that that breakpoint is
4219 after the program encounters a breakpoint. This is often the
4220 number of bytes in `BREAKPOINT', though not always. For most
4246 breakpoint. It takes a `CORE_ADDR *' as argument, and stores the
4283 necessary to set a breakpoint to get through the dynamic linker
4389 (including space for a breakpoint) to which the called function
4392 Set BP_ADDR to the address at which the breakpoint instruction
4397 (*note frame_align::) breakpoint, BP_ADDR is set to the address
4398 reserved for that breakpoint, and REAL_PC set to FUNADDR.
4443 Advance the inferior's PC past a permanent breakpoint. GDB
4444 normally steps over a breakpoint by removing it, stepping one
4445 instruction, and re-inserting the breakpoint. However, permanent
4449 so that execution will resume just after the breakpoint. This
4450 function does the right thing even when the breakpoint is in the
4550 Define this to be the 4-bit location of the breakpoint trap
6663 Breakpoint 1 at 0x80732bc: file main.c, line 734.
6667 Breakpoint 1, main (argc=1, argv=0xbffff8b4) at main.c:734
7216 emacs, or run GDB on itself and set a breakpoint in `execute_command'.
7381 execution stops due to a breakpoint, and this breakpoint has a
7382 condition that is not met. If the breakpoint has any associated
7464 A new breakpoint has been created. The argument BPNUM is the
7465 number of the newly-created breakpoint.
7468 A breakpoint has been destroyed. The argument BPNUM is the number
7469 of the newly-destroyed breakpoint.
7472 A breakpoint has been modified in some way. The argument BPNUM is
7473 the number of the modified breakpoint.
8071 * BREAKPOINT: Defining Other Architecture Features.
8073 * breakpoint address adjusted: Defining Other Architecture Features.
8448 * insert or remove hardware breakpoint: Algorithms. (line 234)
8450 * insert or remove software breakpoint: Algorithms. (line 211)
