+2020-01-14 Luis Machado <luis.machado@linaro.org>
+
+ * inf-ptrace.c (inf_ptrace_target::resume): Update comments.
+ * infrun.c (resume_1): Likewise.
+ (handle_inferior_event): Remove stale comment.
+ * linux-nat.c (linux_nat_target::resume): Update comments.
+ (save_stop_reason): Likewise.
+ (linux_nat_filter_event): Likewise.
+ * linux-nat.h (struct lwp_info) <stop_pc>, <stop_reason>: Likewise.
+
2020-01-13 Andrew Burgess <andrew.burgess@embecosm.com>
* elfread.c (record_minimal_symbol): Set section index to 0 for
if (step)
{
/* If this system does not support PT_STEP, a higher level
- function will have called single_step() to transmute the step
- request into a continue request (by setting breakpoints on
- all possible successor instructions), so we don't have to
- worry about that here. */
+ function will have called the appropriate functions to transmute the
+ step request into a continue request (by setting breakpoints on
+ all possible successor instructions), so we don't have to
+ worry about that here. */
request = PT_STEP;
}
if (tp->control.trap_expected || bpstat_should_step ())
tp->control.may_range_step = 0;
- /* If enabled, step over breakpoints by executing a copy of the
- instruction at a different address.
+ /* If displaced stepping is enabled, step over breakpoints by executing a
+ copy of the instruction at a different address.
We can't use displaced stepping when we have a signal to deliver;
the comments for displaced_step_prepare explain why. The
&& step_over_info_valid_p ())
{
/* If we have nested signals or a pending signal is delivered
- immediately after a handler returns, might might already have
+ immediately after a handler returns, might already have
a step-resume breakpoint set on the earlier handler. We cannot
set another step-resume breakpoint; just continue on until the
original breakpoint is hit. */
stop_waiting (ecs);
return;
- /* The following are the only cases in which we keep going;
- the above cases end in a continue or goto. */
case TARGET_WAITKIND_FORKED:
case TARGET_WAITKIND_VFORKED:
/* Check whether the inferior is displaced stepping. */
resume_many = (minus_one_ptid == ptid
|| ptid.is_pid ());
- /* Mark the lwps we're resuming as resumed. */
+ /* Mark the lwps we're resuming as resumed and update their
+ last_resume_kind to resume_continue. */
iterate_over_lwps (ptid, resume_set_callback);
/* See if it's the current inferior that should be handled
{
/* If we determine the LWP stopped for a SW breakpoint,
trust it. Particularly don't check watchpoint
- registers, because at least on s390, we'd find
+ registers, because, at least on s390, we'd find
stopped-by-watchpoint as long as there's a watchpoint
set. */
lp->stop_reason = TARGET_STOPPED_BY_SW_BREAKPOINT;
}
/* Check if we should go on and pass this event to common code.
- Return the affected lwp if we are, or NULL otherwise. */
+ Return the affected lwp if we should, or NULL otherwise. */
static struct lwp_info *
linux_nat_filter_event (int lwpid, int status)
/* Don't report signals that GDB isn't interested in, such as
signals that are neither printed nor stopped upon. Stopping all
- threads can be a bit time-consuming so if we want decent
+ threads can be a bit time-consuming, so if we want decent
performance with heavily multi-threaded programs, especially when
they're using a high frequency timer, we'd better avoid it if we
can. */
/* When 'stopped' is set, this is where the lwp last stopped, with
decr_pc_after_break already accounted for. If the LWP is
- running, and stepping, this is the address at which the lwp was
+ running and stepping, this is the address at which the lwp was
resumed (that is, it's the previous stop PC). If the LWP is
running and not stepping, this is 0. */
CORE_ADDR stop_pc;
int step;
/* The reason the LWP last stopped, if we need to track it
- (breakpoint, watchpoint, etc.) */
+ (breakpoint, watchpoint, etc.). */
enum target_stop_reason stop_reason;
/* On architectures where it is possible to know the data address of
projects / deliverable / binutils-gdb.git / commitdiff
