gdb/gdb/infttrace.c

230    "other threads run during step", we have some stuff to do:
238       step finish on that thread, which can lead to complications;
246    be off the list for a while, it's possible the step will complete
251    step/continue during the scan.
271    re-scan a lot.  By observation, it looks like a single-step/wait
337 /* This flag is true if we are doing a step-over-bpt
364     stepping_mode_t stepping_mode;	/* Whether to step or continue */
1183   printf (", step is %s", get_printable_name_of_stepping_mode (p->stepping_mode));
1250          operation, which is a multiple step thing, to the point where we
1815    * we always return the result of a fake-step first.
1831       /* Did we just single-step a single thread, without letting any
1843 	   * successful completion of a step) or a SYSCALL_ENTRY
1844 	   * (due to a step completion with active hardware
1848 	    printf ("Ending fake step with tid %d, state %s\n",
1898        * see a fake-step later on in the scan).
1918 	  /* Fake step.
1924 	  warning ("Internal error: fake-step failed to complete.");
2065    *                        Stopped   Running    Fake-step  (v)Fork
2155    * _know_ it's going to complete the single-step we
2156    * asked for (because we're only doing the step under
2167 	printf ("Doing a wait after a fake-step for %d, pid %d\n",
2282       /* This wait clears the (current) fake-step if there was one.
2811      get for a single-step completion.  This should cause wait_for_inferior
2818      event.  So, we'll single-step the inferior to get out of the syscall,
2823      step out of one syscall only to immediately enter another...
3943     printf ("Using loop over threads to step/resume with signals\n");
4003   /* Now run down the thread list and continue or step.
4030 	      /* Just step this thread.
4192       printf ("Doing a fake-step over a bpt, etc. for %d\n", tid);
4200     warning ("Step while step already in progress.");
4284  *   If STEP is nonzero,   single-step it.
4308 child_resume (ptid_t ptid, int step, enum target_signal signal)
4344 	  if (step == 0)
4351 	  if (step == 0)
4363     warning ("Internal error in resume logic; doing resume or step anyway.");
4365   if (!step			/* Asked to continue...       */
4403   /* Are we faking this "continue" or "step"?
4410    * and one thread is in the join, and the user wants to step that
4418       if (!step)
4435 	    printf ("Faking a process step.\n");
4462 	  if (step)
4469     }				/* Must fake step or go */
4482    * have called single_step() to transmute the step request into a
4486   if (step)
4491 	   * Regular user step: other threads get a "continue".
4500 	  /* "Fake step": gdb is stepping one thread over a
4505 	   * step the current thread, but leave the rest stopped.
5460    we can always set a regular (aka single-step & test) watchpoint