unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
Cc: 28630@debbugs.gnu.org, tom@tromey.com, agrambot@gmail.com
Subject: bug#28630: 27.0.50; C-g while a non-main thread is sitting crashes Emacs
Date: Mon, 09 Oct 2017 11:38:33 +0300	[thread overview]
Message-ID: <838tgksol2.fsf@gnu.org> (raw)
In-Reply-To: <wltvz8eno8.wl%mituharu@math.s.chiba-u.ac.jp> (message from YAMAMOTO Mitsuharu on Mon, 09 Oct 2017 17:21:59 +0900)

> Date: Mon, 09 Oct 2017 17:21:59 +0900
> From: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>
> Cc: YAMAMOTO Mitsuharu <mituharu@math.s.chiba-u.ac.jp>, agrambot@gmail.com,
>  28630@debbugs.gnu.org, tom@tromey.com
> 
> > For the record, on MS-Windows, both are interrupted.
> 
> I could make the Mac port interruptible also for Example 2 (with some
> delay because it uses polling with SIGALRM rather than SIGIO).  I also
> confirmed that Motif behaved like Athena.  Below is updated one:

Thanks, more commonality in behavior is good, I think.

> In principle, the method I used for the Mac port is also applicable to
> X11 (but probably not for NS where secondary threads cannot read
> keyboard input).  Each pselect call not involving keyboard input
> additionally monitors one side of a socket pair, and the SIGALRM
> handler writes to the other side.  This way, a pselect call in a
> secondary thread is unblocked when the signal arrived, and then it
> tries to see if keyboard input is available when none of other threads
> is monitoring the keyboard input channel.

But the problematic part in these examples is that the main thread
always waits for keyboard input, because the non-main thread starts
running only when the main thread becomes idle, and becoming idle
means calling pselect.  And since the main thread is always the first
one to call pselect, it is the thread which finds the keyboard
descriptor unmonitored, and installs itself as its monitoring thread.

So with your proposal, more often than not, the "none of other threads
is monitoring the keyboard input channel" part will never be true,
except for the main thread.  Or am I missing something?

> Having said that, I don't think we need the change like this urgently.
> For now, we can see if the above method really works for more
> complicated situations using the Mac port.

I agree.  So far, I've only seen toy programs, and it isn't clear to
me how serious those problems are in real life.





  reply	other threads:[~2017-10-09  8:38 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-28  7:22 bug#28630: 27.0.50; C-g while a non-main thread is sitting crashes Emacs Alex
2017-10-01  3:18 ` Alex
2017-10-01 15:01   ` Eli Zaretskii
2017-10-01 18:10     ` Alex
2017-10-01 18:32       ` Eli Zaretskii
2017-10-02  4:30         ` YAMAMOTO Mitsuharu
2017-10-02 12:43           ` YAMAMOTO Mitsuharu
2017-10-02 16:08             ` Eli Zaretskii
2017-10-04  7:39               ` Eli Zaretskii
2017-10-04  7:49                 ` YAMAMOTO Mitsuharu
2017-10-04  8:16                   ` Eli Zaretskii
2017-10-04  8:32                     ` YAMAMOTO Mitsuharu
2017-10-04  9:23                       ` Eli Zaretskii
2017-10-05  3:27                         ` YAMAMOTO Mitsuharu
2017-10-05  7:24                           ` Eli Zaretskii
2017-10-07 13:53                             ` Philipp Stephani
2017-10-07 14:24                               ` Eli Zaretskii
2017-10-07 14:50                                 ` Eli Zaretskii
2017-10-09  8:21                             ` YAMAMOTO Mitsuharu
2017-10-09  8:38                               ` Eli Zaretskii [this message]
2017-10-09 10:34                                 ` mituharu
2017-10-09 11:01                                   ` Eli Zaretskii
2017-10-04  7:39               ` YAMAMOTO Mitsuharu
2017-10-04  8:14                 ` Eli Zaretskii
2017-10-02  5:11         ` Eric Abrahamsen
2017-10-02 15:54           ` Eli Zaretskii
2017-10-03  9:35         ` Dmitry Gutov
2017-10-03 14:38           ` Eli Zaretskii
2017-10-03 14:50             ` Philipp Stephani
2017-10-03 15:45               ` Eli Zaretskii
2017-10-03 16:22                 ` Philipp Stephani
2017-10-03 16:35                   ` Eli Zaretskii
2017-10-03 17:04                     ` Philipp Stephani
2017-10-01 10:08 ` Alan Third
2017-10-01 15:03   ` Eli Zaretskii

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=838tgksol2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=28630@debbugs.gnu.org \
    --cc=agrambot@gmail.com \
    --cc=mituharu@math.s.chiba-u.ac.jp \
    --cc=tom@tromey.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).