From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: the state of the concurrency branch Date: Wed, 28 Aug 2013 19:23:20 +0300 Message-ID: <831u5dg4xz.fsf@gnu.org> References: <87vc2t7erx.fsf@fleche.redhat.com> <83txicffpe.fsf@gnu.org> <87haeb3lwp.fsf@fleche.redhat.com> <83mwo3f762.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1377707017 32401 80.91.229.3 (28 Aug 2013 16:23:37 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 28 Aug 2013 16:23:37 +0000 (UTC) Cc: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org To: tromey@redhat.com Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 28 18:23:36 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VEiWt-0005DA-P5 for ged-emacs-devel@m.gmane.org; Wed, 28 Aug 2013 18:23:35 +0200 Original-Received: from localhost ([::1]:37234 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEiWt-0003n8-Bm for ged-emacs-devel@m.gmane.org; Wed, 28 Aug 2013 12:23:35 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58037) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEiWm-0003lu-Ak for emacs-devel@gnu.org; Wed, 28 Aug 2013 12:23:33 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VEiWh-00013h-7N for emacs-devel@gnu.org; Wed, 28 Aug 2013 12:23:28 -0400 Original-Received: from mtaout20.012.net.il ([80.179.55.166]:55345) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VEiWg-00013Z-VZ for emacs-devel@gnu.org; Wed, 28 Aug 2013 12:23:23 -0400 Original-Received: from conversion-daemon.a-mtaout20.012.net.il by a-mtaout20.012.net.il (HyperSendmail v2007.08) id <0MS9007001EFVB00@a-mtaout20.012.net.il> for emacs-devel@gnu.org; Wed, 28 Aug 2013 19:23:21 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by a-mtaout20.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0MS9007JC1IWRY40@a-mtaout20.012.net.il>; Wed, 28 Aug 2013 19:23:21 +0300 (IDT) In-reply-to: <83mwo3f762.fsf@gnu.org> X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: Solaris 10 X-Received-From: 80.179.55.166 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:163078 Archived-At: > Date: Tue, 27 Aug 2013 19:08:21 +0300 > From: Eli Zaretskii > Cc: lekktu@gmail.com, monnier@iro.umontreal.ca, emacs-devel@gnu.org > > . Will the handling of SIGCHLD be thread-specific or global? IOW, if > a thread fires up a subprocess, which exits while another thread is > running, which thread(s) will get the signal? If the signal > arrives at some other thread, how will that thread know to handle > it, if it doesn't watch the corresponding fd's? Please answer this question, if you can: I need the answer to analyze what, if any, changes are needed in how Emacs on Windows handles process demise and emulates SIGCHLD. Currently, we watch all of the subprocesses inside the 'pselect' call; the question is: should we only watch those of them that are relevant to the thread that calls 'pselect'. TIA