From: Eli Zaretskii <eliz@gnu.org>
To: Pedro Alves <palves@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] stepi/nexti: skip signal handler if "handle nostop" signal arrives
Date: Wed, 15 Oct 2014 14:31:00 -0000 [thread overview]
Message-ID: <838ukh5rry.fsf@gnu.org> (raw)
In-Reply-To: <543E7961.5090002@redhat.com>
> Date: Wed, 15 Oct 2014 14:40:49 +0100
> From: Pedro Alves <palves@redhat.com>
> CC: gdb-patches@sourceware.org
>
> On 10/14/2014 08:22 PM, Eli Zaretskii wrote:
> >> Date: Tue, 14 Oct 2014 19:49:40 +0100
> >> From: Pedro Alves <palves@redhat.com>
>
> > I think this text mixes 2 different things: (1) how the signal
> > handling affects whether the signal gets to the program or not, and is
> > it announced or not; and (2) the fine details of when the signal
> > becomes "known" to the program and how stepping commands affect and
> > are affected by that.
> >
> > It might be the simplest to separate the two issues, and describe each
> > one on its own.
>
> I'll give that a try.
Thanks. Let me know if I can help.
> >> No, we intercept the signal before the program sees it. See above.
> >
> > But you wrote "the program stops for a signal". "The program stops"
> > means (or at least could be interpreted as meaning) the signal was
> > already seen by the program, and the program then stopped.
> >
> > See how this is confusing?
>
> I don't see how one would be confused, as the paragraph just above
> says "When a signal stops your program", and I feel that the that
> wording I chose follows naturally from that.
As long as we didn't try to talk about fine details that happen at
that time, it was okay.
> I'll come up with a new version once I have a chance.
Thanks in advance.
next prev parent reply other threads:[~2014-10-15 14:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-14 17:48 Pedro Alves
2014-10-14 18:27 ` Eli Zaretskii
2014-10-14 18:49 ` Pedro Alves
2014-10-14 18:56 ` Pedro Alves
2014-10-14 19:22 ` Eli Zaretskii
2014-10-15 13:40 ` Pedro Alves
2014-10-15 14:31 ` Eli Zaretskii [this message]
2014-10-25 14:00 ` Pedro Alves
2014-10-27 17:39 ` Eli Zaretskii
2014-10-27 19:44 ` Pedro Alves
2014-10-27 19:58 ` Eli Zaretskii
2014-10-27 20:34 ` Pedro Alves
2014-10-15 11:12 ` Yao Qi
2014-10-15 13:44 ` Pedro Alves
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838ukh5rry.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox