From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Mikael Djurfeldt Newsgroups: gmane.lisp.guile.devel Subject: Re: Warning: Unstable POSIX threads support comitted to CVS Date: Mon, 09 Dec 2002 18:40:40 +0100 Sender: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Message-ID: References: Reply-To: djurfeldt@nada.kth.se NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1039456092 19663 80.91.224.249 (9 Dec 2002 17:48:12 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 9 Dec 2002 17:48:12 +0000 (UTC) Cc: djurfeldt@nada.kth.se Return-path: Original-Received: from monty-python.gnu.org ([199.232.76.173]) by main.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 18LS0j-00055x-00 for ; Mon, 09 Dec 2002 18:48:05 +0100 Original-Received: from localhost ([127.0.0.1] helo=monty-python.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18LRu0-00068s-03 for guile-devel@m.gmane.org; Mon, 09 Dec 2002 12:41:08 -0500 Original-Received: from list by monty-python.gnu.org with tmda-scanned (Exim 4.10.13) id 18LRtm-00067z-00 for guile-devel@gnu.org; Mon, 09 Dec 2002 12:40:54 -0500 Original-Received: from mail by monty-python.gnu.org with spam-scanned (Exim 4.10.13) id 18LRtd-00066L-00 for guile-devel@gnu.org; Mon, 09 Dec 2002 12:40:47 -0500 Original-Received: from kvast.blakulla.net ([213.212.20.77]) by monty-python.gnu.org with esmtp (Exim 4.10.13) id 18LRtd-000664-00 for guile-devel@gnu.org; Mon, 09 Dec 2002 12:40:45 -0500 Original-Received: from barbara.blakulla.net ([213.212.21.238] helo=linnaeus) by kvast.blakulla.net with esmtp (Exim 3.36 #1 (Debian)) id 18LRtZ-0003cP-00; Mon, 09 Dec 2002 18:40:41 +0100 Original-Received: from mdj by linnaeus with local (Exim 3.36 #1 (Debian)) id 18LRtZ-0006CN-00; Mon, 09 Dec 2002 18:40:41 +0100 Original-To: Marius Vollmer In-Reply-To: (Marius Vollmer's message of "09 Dec 2002 15:26:03 +0100") User-Agent: Gnus/5.090008 (Oort Gnus v0.08) Emacs/21.2 (i386-pc-linux-gnu) Original-cc: guile-devel@gnu.org X-BeenThere: guile-devel@gnu.org X-Mailman-Version: 2.1b5 Precedence: list List-Id: Developers list for Guile, the GNU extensibility library List-Help: List-Post: List-Subscribe: , List-Archive: List-Unsubscribe: , Errors-To: guile-devel-bounces+guile-devel=m.gmane.org@gnu.org Xref: main.gmane.org gmane.lisp.guile.devel:1811 X-Report-Spam: http://spam.gmane.org/gmane.lisp.guile.devel:1811 Marius Vollmer writes: > Mikael Djurfeldt writes: > >> It is very irritating that signals are delivered to whatever thread >> happens to run for the moment. > > Do you refer to the execution of POSIX signal handlers or to the > execution of Scheme signal handlers? With "delivered" I'm thinking of "end-point" delivery, that is execution of Scheme signal handlers. I'm thinking of channeling all signals to a particular target thread (which becomes the one to run its handlers until the target is switched). > That is, signals-plus-threads are quite nasty on Linux. I think we > should have a dedicated signal handling thread that polls for signals > and marks the relevant system asyncs when they arrive. That sounds like a good solution. Are there particular reasons why a dedicated thread is needed rather than that an arbitrary POSIX signal handler of an arbitrary receives the signal sets the asyncs of the "foreground" thread? I guess one such reason could be that we, in that case, could block signals for all threads except the signal one, with the benefit that a particular signal is only received "once" (rather than getting a "barrage" of async marks at asyncronous points in time), right? M _______________________________________________ Guile-devel mailing list Guile-devel@gnu.org http://mail.gnu.org/mailman/listinfo/guile-devel