From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Crashing the new thread code Date: Mon, 12 Dec 2016 05:41:14 +0200 Message-ID: <83oa0hddb9.fsf@gnu.org> References: <87h96a2tyi.fsf@irif.fr> <83twaacii3.fsf@gnu.org> <87d1gy2mat.fsf@irif.fr> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1481514050 2825 195.159.176.226 (12 Dec 2016 03:40:50 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Dec 2016 03:40:50 +0000 (UTC) Cc: jch@irif.fr, emacs-devel@gnu.org To: Noam Postavsky Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 12 04:40:46 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1cGHTq-000885-CK for ged-emacs-devel@m.gmane.org; Mon, 12 Dec 2016 04:40:46 +0100 Original-Received: from localhost ([::1]:58812 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGHTt-00078P-2E for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2016 22:40:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:34014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGHTm-000789-De for emacs-devel@gnu.org; Sun, 11 Dec 2016 22:40:43 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGHTj-0003aU-92 for emacs-devel@gnu.org; Sun, 11 Dec 2016 22:40:42 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:50668) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGHTj-0003aF-06; Sun, 11 Dec 2016 22:40:39 -0500 Original-Received: from 84.94.185.246.cable.012.net.il ([84.94.185.246]:3692 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1cGHTh-0004od-Vd; Sun, 11 Dec 2016 22:40:38 -0500 In-reply-to: (message from Noam Postavsky on Sun, 11 Dec 2016 16:58:49 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:210326 Archived-At: > From: Noam Postavsky > Date: Sun, 11 Dec 2016 16:58:49 -0500 > Cc: Emacs developers , Eli Zaretskii > > >> 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? Please note that the current implementation effectively makes non-main threads run with all errors caught, so signaling an error has much less spectacular consequences than in the main thread.