From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail
From: Eli Zaretskii <eliz@gnu.org>
Newsgroups: gmane.emacs.devel
Subject: Re: Why does this thread code crash my emacs?
Date: Sat, 16 Oct 2021 14:51:20 +0300
Message-ID: <83sfx1gpc7.fsf@gnu.org>
References: <87pms6jmuk.fsf@ddavies.net> <83r1cmi03z.fsf@gnu.org>
Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214";
	logging-data="23552"; mail-complaints-to="usenet@ciao.gmane.io"
Cc: emacs-devel@gnu.org
To: ddavies@ddavies.net
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Oct 16 13:52:36 2021
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane-mx.org
Original-Received: from lists.gnu.org ([209.51.188.17])
	by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
	(Exim 4.92)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1mbiEt-0005yh-Ud
	for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 13:52:35 +0200
Original-Received: from localhost ([::1]:59088 helo=lists1p.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.90_1)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>)
	id 1mbiEs-0004YD-Eb
	for ged-emacs-devel@m.gmane-mx.org; Sat, 16 Oct 2021 07:52:34 -0400
Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:40472)
 by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>) id 1mbiDf-0003kB-Sg
 for emacs-devel@gnu.org; Sat, 16 Oct 2021 07:51:19 -0400
Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:46084)
 by eggs.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <eliz@gnu.org>)
 id 1mbiDf-00009X-FC; Sat, 16 Oct 2021 07:51:19 -0400
Original-Received: from [87.69.77.57] (port=3224 helo=home-c4e4a596f7)
 by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
 (Exim 4.90_1) (envelope-from <eliz@gnu.org>)
 id 1mbiDf-0006L3-2Q; Sat, 16 Oct 2021 07:51:19 -0400
In-Reply-To: <83r1cmi03z.fsf@gnu.org> (message from Eli Zaretskii on Fri, 15
 Oct 2021 22:01:04 +0300)
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
 <mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org
Original-Sender: "Emacs-devel"
 <emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org>
Xref: news.gmane.io gmane.emacs.devel:277169
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/277169>

> Date: Fri, 15 Oct 2021 22:01:04 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: emacs-devel@gnu.org
> 
> You currently cannot signal a thread that is waiting for input (hanoi
> waits for input inside sit-for), because Emacs doesn't (yet) know how
> to recover from signals in that state.
> 
> IOW, this is a limitation of the current implementation that is more
> visible when signaling threads than when there's only one (main)
> thread.

I've now attempted to fix this on the emacs-28 branch.  Hopefully,
this won't have any adverse effects elsewhere, otherwise we'd have to
move this to master, and continue debugging that.