Re: [PATCH] stepi/nexti: skip signal handler if "handle nostop" signal arrives

Eli Zaretskii
2014-10-14T18:27:40Z

> From: Pedro Alves <palves@redhat.com>
> Date: Tue, 14 Oct 2014 18:48:30 +0100
>
> --- a/gdb/doc/gdb.texinfo
> +++ b/gdb/doc/gdb.texinfo
> @@ -5526,6 +5526,11 @@ Their full names are:
> @value{GDBN} should not stop your program when this signal happens. It may
> still print a message telling you that the signal has come in.
>
> +If this signal arrives while a stepping command (e.g., @code{step}) is
> +in progress, the signal's handler is skipped (though still executed if
> +@code{pass} is in effect; see below). @value{GDBN} will still stop
> +your program if the handler hits a breakpoint.

This description is confusing. For starters, it only mentions some of
the possible setting of signal handling, and keeps silence about the
rest. Either we should describe what happens with all of them, one by
one, or (better) says something that will explain how we handle them
all, at once.

Also, I believe the description of stepping should mention this
aspect, with a cross-reference to here.

> +If a stepping command is issued after the program stops for a signal,
> +and @code{pass} is in effect for that signal, @value{GDBN} steps into
> +the signal's handler (if the target supports it).

Again, this left me wondering. E.g., if the program stops for a
signal, then we are already in the signal handler, no? So the fact
that stepping commands continue there is a no-brainer, right? Or a I
again confused?

Thanks.