From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Noam Postavsky Newsgroups: gmane.emacs.devel Subject: Re: Crashing the new thread code Date: Sun, 11 Dec 2016 23:10:48 -0500 Message-ID: References: <87h96a2tyi.fsf@irif.fr> <83twaacii3.fsf@gnu.org> <87d1gy2mat.fsf@irif.fr> <83oa0hddb9.fsf@gnu.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1481516153 19945 195.159.176.226 (12 Dec 2016 04:15:53 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Mon, 12 Dec 2016 04:15:53 +0000 (UTC) Cc: Juliusz Chroboczek , Emacs developers To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 12 05:15:48 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 1cGI1k-0004VC-3w for ged-emacs-devel@m.gmane.org; Mon, 12 Dec 2016 05:15:48 +0100 Original-Received: from localhost ([::1]:60228 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGI1o-0002iF-Ai for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2016 23:15:52 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:46021) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGHxy-0008JJ-4c for emacs-devel@gnu.org; Sun, 11 Dec 2016 23:11:55 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGHxx-00060x-CV for emacs-devel@gnu.org; Sun, 11 Dec 2016 23:11:54 -0500 Original-Received: from mail-oi0-f68.google.com ([209.85.218.68]:36194) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cGHxt-00060R-Ma; Sun, 11 Dec 2016 23:11:49 -0500 Original-Received: by mail-oi0-f68.google.com with SMTP id u15so9478377oie.3; Sun, 11 Dec 2016 20:11:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=g4pf8LGp/DSvczrKj/tQ1bSlOE3DTa6gutZLm6s6dgg=; b=ysDpeflXQ/KILJgeIyuCKm3c1mI7fZ+nuIseAXroCABue3t0U7gn3noLP2zMPNSuoc YJA8NSNEUpWkcxK7HrkYTzq3CV/I9b6JTiJrZ15ff1kHglN4XocQdzTfua+Izde3DHje CgKdLsDRw1aT1LIllLtejh4LGqK85DFD4knnYoWcTRxocOUXw8lsLa8SU8NGDjo3Add4 4CgTVmHaqIBTRffpFqmLo8pX6B0P+02HujD6TtuLW7RaCi8GW+YaLsk6kO9v216u1uE5 4HcaCcoHk8L5l/rV8pK9MkU4jHYYnuHFaFC2FioJY6bBkvOtMFHSkrAgzUdgsrPSetLZ oODw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=g4pf8LGp/DSvczrKj/tQ1bSlOE3DTa6gutZLm6s6dgg=; b=ECwmn3H0m/u/pX0yiagT+DAXQs1sh4SBtL31f4fxzaWVOUTxy2ZdDyoBj2PrsXWMGB XBVgtu1gFCVyYKMtVGCl8l13CjoVXtyEXajWXzND03VVHbSmSNI23rNktO8m5y1L1+Zp IMDZOMWUVdgM/dkHwun+pgZtlxHtVBfdP0Wd1UualqBNC6jC6t86WAD+7xvCBB6SgUQO Jvrw+hzWeuMn5+FDhAKgqq9VArvskAzwxAW/kk9VMv64vUERzDngHr7qASoiKE5j1Yh7 1k3f0IspANRIf6v11smQkzYRx/O8Jjoglp6p8R1HG0SXuWHN1dgNnyY8Yv2nkYLJDKpu VrWg== X-Gm-Message-State: AKaTC00N0UMh8iMEIaY55PNNqSy3ci20D01I7+2VGbPHS9fMmX0f1t4+Zw2dwd7Ne2Ze5rzRRXXmTVM2N2hu+w== X-Received: by 10.157.9.72 with SMTP id 66mr36053116otp.109.1481515848688; Sun, 11 Dec 2016 20:10:48 -0800 (PST) Original-Received: by 10.157.6.234 with HTTP; Sun, 11 Dec 2016 20:10:48 -0800 (PST) In-Reply-To: <83oa0hddb9.fsf@gnu.org> X-Google-Sender-Auth: u_khFtAEsIQzcUETFh_RetWJgbQ X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.218.68 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:210327 Archived-At: On Sun, Dec 11, 2016 at 10:41 PM, Eli Zaretskii wrote: >> 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? 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. > > 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.