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 16:58:49 -0500 Message-ID: References: <87h96a2tyi.fsf@irif.fr> <83twaacii3.fsf@gnu.org> <87d1gy2mat.fsf@irif.fr> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: blaine.gmane.org 1481493604 30923 195.159.176.226 (11 Dec 2016 22:00:04 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Sun, 11 Dec 2016 22:00:04 +0000 (UTC) Cc: Eli Zaretskii , Emacs developers To: Juliusz Chroboczek Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Dec 11 23:00:00 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 1cGCA4-0007Km-7q for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2016 23:00:00 +0100 Original-Received: from localhost ([::1]:57293 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGCA8-00061D-BF for ged-emacs-devel@m.gmane.org; Sun, 11 Dec 2016 17:00:04 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:43809) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cGC9z-000616-T9 for emacs-devel@gnu.org; Sun, 11 Dec 2016 16:59:59 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cGC9v-0006po-4g for emacs-devel@gnu.org; Sun, 11 Dec 2016 16:59:56 -0500 Original-Received: from mail-oi0-f48.google.com ([209.85.218.48]:34696) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cGC9u-0006pY-VC; Sun, 11 Dec 2016 16:59:51 -0500 Original-Received: by mail-oi0-f48.google.com with SMTP id y198so70995092oia.1; Sun, 11 Dec 2016 13:59:50 -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=zj1z/q779wmThrvoFhzuE9ZfD5I2i6BEJxg0AtV17ow=; b=mXCi7n1iQhST54pw9xxJNK+L5ySHzABGtm4lEFlFtr6kjs8Iy19SPh5lSl+S5bb37I J88GYZniGA7bsTrq10KeGw1AA1vFusyeo0pSsXy5r/6wr7MvuYy3480nNKpCA34Tb5V7 hFUDKte4QBaBAvzHAytG3VE9gdWBg/pPD78+xtIrSQ691gZ98p5QoV+MbA/6xWNjfMoh 48IPuviJ0JjW4z2/W/5oedyOP9pWH9S2xWOODaAF3rGV7Q072ILUh70NaFxFKgFG1mnM Rp88yuhBsnMVgBY1BYFKMypzGWiw96UhLcqXEByZhFnYDb2pD/XV/vd40/5EUC6ryl1u xN9A== 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=zj1z/q779wmThrvoFhzuE9ZfD5I2i6BEJxg0AtV17ow=; b=ICtYjEYiT7JqOP8uvcmFe6avrvZb3VlJuvA0G+cb1YIPiKmhOgTno2DmPvx1MzLr24 ogcn5xbZEqK2FUdren5REzyXCoE2l05MqPVtd0zE2c3CiJbWPnd1Lw8/DdGnurmMmAq9 KlO3Fx39WIei+sN4Vd+1vcWgzAvIdMyDR8W4iORPa3C0qC474tKtigMtLkQWQLbmEn0Z OzanQ+jRTAaChanZFdizul8kPDxTERO3EbKegupRydiJ38QKeyGlajVC5QxhdajegW5J Lt8+ogz89oODkrfARcgUquc+e/0H+bAJYcY/oxeqCWb6JVPRBcA5mUfqCp6I2fTWIv6k j+vA== X-Gm-Message-State: AKaTC03ie2gSMwyU7sHtgTLpDmpzV7IB+DgfO2UmwzWEnOgLXjt1ZmKdfKpJDBPnGckV4JXR75/AX8pIgTZTrQ== X-Received: by 10.202.192.133 with SMTP id q127mr23379310oif.128.1481493529854; Sun, 11 Dec 2016 13:58:49 -0800 (PST) Original-Received: by 10.157.6.234 with HTTP; Sun, 11 Dec 2016 13:58:49 -0800 (PST) In-Reply-To: <87d1gy2mat.fsf@irif.fr> X-Google-Sender-Auth: MvXc0dR6eqBKuLB0_e_mlsZASjs X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] [fuzzy] X-Received-From: 209.85.218.48 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:210316 Archived-At: On Sun, Dec 11, 2016 at 4:22 PM, Juliusz Chroboczek wrote: >>> The following immediately crashes Emacs: >>> >>> (let ((thread (make-thread #'(lambda () (while t (thread-yield)))))) >>> (thread-signal thread 'error nil)) > >> What is the semantics of signaling a thread that yields? > > I'm not sure, that's why I was experimenting. > >> 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.