Lines Matching refs:breakpoint
85 stepped over was a breakpoint). The value of $eip will be the
88 SIGTRAP when we hit a breakpoint. The value of $eip will be
89 the instruction after the breakpoint (i.e. needs to be
96 If we single-step over a breakpoint instruction, our PC will
98 breakpoint instruction, our PC will point at the breakpoint
263 /* Return nonzero if this process stopped at a breakpoint which
265 appropriately to resume where the breakpoint used to be. */
276 fprintf (stderr, "Checking for breakpoint.\n");
296 /* If the breakpoint is still there, we will report hitting it. */
300 fprintf (stderr, "Ignoring, breakpoint is still present.\n");
306 fprintf (stderr, "Removed breakpoint.\n");
333 /* This thread was stopped at a breakpoint, and the breakpoint
335 so GDB isn't trying to single-step past this breakpoint.
337 the breakpoint just after it was removed instead of just
402 it stopped. We correctly handle the change of PC if we hit a breakpoint
523 a gdbserver breakpoint; single-stepping to/over one
528 fprintf (stderr, "Reinserted breakpoint.\n");
538 fprintf (stderr, "Hit a (non-reinsert) breakpoint.\n");
543 breakpoint, so that check_removed_breakpoint () will do the PC
548 /* Now we need to put the breakpoint back. We continue in the event
549 loop instead of simply replacing the breakpoint right away,
551 breakpoint. Unfortunately this increases the window where another
552 thread could sneak past the removed breakpoint. For the current
554 acceptable; but it needs to be considered before this breakpoint
560 use PT_STEP on this platform. Uninsert the breakpoint,
564 our temporary breakpoint, create it, and continue executing this
597 /* A SIGTRAP that we can't explain. It may have been a breakpoint.
598 Check if it is a breakpoint, and if so mark the process information
601 hitting a breakpoint if two hit it at once and then GDB removes it
786 breakpoint; it will be picked up again below. */
840 a breakpoint. */
964 /* If this thread has a removed breakpoint, we won't have any
968 lets us preserve stopped status when two threads hit a breakpoint.
969 GDB removes the breakpoint to single-step a particular thread
1262 set_breakpoint_data (the_low_target.breakpoint,