From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Pretest next week Date: Mon, 26 Jan 2009 19:42:36 -0500 Message-ID: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1233597973 4918 80.91.229.12 (2 Feb 2009 18:06:13 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 2 Feb 2009 18:06:13 +0000 (UTC) Cc: emacs-devel@gnu.org To: Adrian Robert Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Feb 02 19:07:27 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LU3CK-0007le-Us for ged-emacs-devel@m.gmane.org; Mon, 02 Feb 2009 19:07:05 +0100 Original-Received: from localhost ([127.0.0.1]:54718 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LU3B2-0006Lh-B8 for ged-emacs-devel@m.gmane.org; Mon, 02 Feb 2009 13:05:44 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LU38O-0005E1-QE for emacs-devel@gnu.org; Mon, 02 Feb 2009 13:03:00 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LU38N-0005DG-8u for emacs-devel@gnu.org; Mon, 02 Feb 2009 13:03:00 -0500 Original-Received: from [199.232.76.173] (port=39395 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LU38M-0005D7-Tj for emacs-devel@gnu.org; Mon, 02 Feb 2009 13:02:58 -0500 Original-Received: from ironport2-out.pppoe.ca ([206.248.154.182]:39883 helo=ironport2-out.teksavvy.com) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LU38M-0001rb-Ck for emacs-devel@gnu.org; Mon, 02 Feb 2009 13:02:58 -0500 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AswEACTEhknO+IQk/2dsb2JhbACBbso/hBQGgmw X-IronPort-AV: E=Sophos;i="4.37,366,1231131600"; d="scan'208";a="33211770" Original-Received: from 206-248-132-36.dsl.teksavvy.com (HELO pastel.home) ([206.248.132.36]) by ironport2-out.teksavvy.com with ESMTP; 02 Feb 2009 13:02:58 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id C28988229; Mon, 2 Feb 2009 13:02:57 -0500 (EST) User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:108613 Archived-At: > Yes, signal() IS called with SIGIO, input_available_signal(), and the latter > is never called (according to an fprintf which works fine running under X). > I also tried calling signal() at various later times, in case the handler > gets replaced. What happens if you do a "kill -IO <...>" from the shell? Is your fprintf properly executed? I.e. is it that the proicess doesn't receive any IO signal or is it that those signals don't invoke your signal handler? Also, could it be that the signals get delivered to another thread? Stefan