From: Eli Zaretskii <eliz@gnu.org>
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: jch@irif.fr, emacs-devel@gnu.org
Subject: Re: Crashing the new thread code
Date: Mon, 12 Dec 2016 19:11:17 +0200 [thread overview]
Message-ID: <83a8c1cbt6.fsf@gnu.org> (raw)
In-Reply-To: <CAM-tV-8hkQhfptfu-hhqM6+1d_QNHym+9Rvaig4MMNsX4dp73Q@mail.gmail.com> (message from Noam Postavsky on Sun, 11 Dec 2016 23:10:48 -0500)
> From: Noam Postavsky <npostavs@users.sourceforge.net>
> Date: Sun, 11 Dec 2016 23:10:48 -0500
> Cc: Juliusz Chroboczek <jch@irif.fr>, Emacs developers <emacs-devel@gnu.org>
>
> On Sun, Dec 11, 2016 at 10:41 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> >> From: Noam Postavsky <npostavs@users.sourceforge.net>
> >> Date: Sun, 11 Dec 2016 16:58:49 -0500
> >> Cc: Emacs developers <emacs-devel@gnu.org>, Eli Zaretskii <eliz@gnu.org>
> >>
> >> >> What did you expect to happen?
> >> >
> >> > The thread queues the condition and continues spinning?
> >>
> >> I would expect the thread to receive the signal as soon as it starts
> >> running again.
> >
> > What would be the indication of the thread receiving the signal? Both
> > in general and specifically in Juliusz's snippet?
>
> In general, that any condition-case or unwind-protect forms should
> run. Since Juliusz's snippet had no other signal catching constructs,
> the signaled thread would just exit, I suppose.
OK, this is how the latest master will behave.
The original problem happened because the new thread was trying to
signal itself before the signal handlers were set up, and actually
before the thread function was even running.
Thanks.
prev parent reply other threads:[~2016-12-12 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-11 18:37 Crashing the new thread code Juliusz Chroboczek
2016-12-11 20:34 ` Eli Zaretskii
2016-12-11 21:22 ` Juliusz Chroboczek
2016-12-11 21:58 ` Noam Postavsky
2016-12-11 22:56 ` Juliusz Chroboczek
2016-12-12 3:41 ` Eli Zaretskii
2016-12-12 4:10 ` Noam Postavsky
2016-12-12 17:11 ` Eli Zaretskii [this message]
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=83a8c1cbt6.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jch@irif.fr \
--cc=npostavs@users.sourceforge.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.