gdb/gdb/infrun.c

127    running.  In this case, we use a step-resume breakpoint to get us
134    address where we can place a step-resume breakpoint to get past the
241 /* Value to pass to target_resume() to cause all threads to resume */
326    followed at the next resume of the inferior, and not
469   /* The next resume of this inferior should bring it to the shlib
484    thread here so that we can resume single-stepping it later.  */
490 /* Things to clean up if we QUIT out of resume ().  */
537 resume (int step, enum target_signal sig)
558   /* Normally, by the time we reach `resume', the breakpoints are either
627 	  /* User-settable 'scheduler' mode requires solo thread resume. */
724    ADDR is the address to resume at, or -1 for resume where stopped.
746       /* If there is a breakpoint at the address we will resume at,
847   resume (oneproc || step || bpstat_should_step (), stop_signal);
907   /* The first resume is not following a fork/vfork/exec. */
1150    sanity check.  There should never be more than one step-resume
1503       /* We may want to consider not doing a resume here in order
1560       resume (0, TARGET_SIGNAL_0);
1565       resume (0, TARGET_SIGNAL_0);
1635          ignore all but the last one.  Just resume the exec'r, and wait
1700       resume (0, TARGET_SIGNAL_0);
1742 	 reported multiple times without an intervening resume.  */
1748   /* We may want to consider not doing a resume here in order to give
1788 	  resume (1, TARGET_SIGNAL_0);
1860 		  /* FIXME MVS: is there any reason not to call resume()? */
1900      the next resume handle it. */
1991       resume (1, 0);
2205          step-resume breakpoint established, right where it should be:
2216          - the existing step-resume breakpoint (which is at the correct
2218          to the new breakpoint, and the old step-resume breakpoint
2262 	/* Need to blow away step-resume breakpoint, as it
2269 	   it is like the step-resume breakpoint.  */
2345 	   simultaneously active step-resume bp's, although the
2350 	   step-resume bp's.  We'll just delete the breakpoint we
2354 	   step-resume bp, but it makes no effort to ensure that
2439 	         breakpoint and resume.  I'm not sure we can without
2510       /* Having a step-resume breakpoint overrides anything
2558 	  /* Set up a step-resume breakpoint at the address
2926 /* We've just entered a callee, and we wish to resume until it returns
3026       resume (currently_stepping (ecs), stop_signal);
3035          decided we should resume from it.
3041       /* If we've just finished a special step resume and we don't
3081       resume (currently_stepping (ecs), stop_signal);
3087 /* This function normally comes after a resume, before