From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: ludo@gnu.org (Ludovic =?iso-8859-1?Q?Court=E8s?=) Newsgroups: gmane.lisp.guile.bugs Subject: Re: signal handling different in 1.8.3 than 1.8.1? Date: Tue, 03 Jun 2008 22:32:11 +0200 Message-ID: <87prqyp8dw.fsf@gnu.org> References: <87d4my8smh.fsf@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1212525166 25921 80.91.229.12 (3 Jun 2008 20:32:46 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 3 Jun 2008 20:32:46 +0000 (UTC) Cc: Gregory Marton To: bug-guile@gnu.org Original-X-From: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Tue Jun 03 22:33:27 2008 Return-path: Envelope-to: guile-bugs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1K3dCA-00033z-Dr for guile-bugs@m.gmane.org; Tue, 03 Jun 2008 22:33:26 +0200 Original-Received: from localhost ([127.0.0.1]:42902 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3dBO-0001qV-0j for guile-bugs@m.gmane.org; Tue, 03 Jun 2008 16:32:38 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K3dBH-0001kB-Ho for bug-guile@gnu.org; Tue, 03 Jun 2008 16:32:31 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K3dBG-0001hf-Ee for bug-guile@gnu.org; Tue, 03 Jun 2008 16:32:30 -0400 Original-Received: from [199.232.76.173] (port=55628 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3dBG-0001hN-Bq for bug-guile@gnu.org; Tue, 03 Jun 2008 16:32:30 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:57184 helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1K3dBF-0007zE-Gf for bug-guile@gnu.org; Tue, 03 Jun 2008 16:32:30 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K3dBD-0001Tu-Nj for bug-guile@gnu.org; Tue, 03 Jun 2008 20:32:28 +0000 Original-Received: from reverse-83.fdn.fr ([80.67.176.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Jun 2008 20:32:27 +0000 Original-Received: from ludo by reverse-83.fdn.fr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Jun 2008 20:32:27 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 46 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: reverse-83.fdn.fr X-URL: http://www.fdn.fr/~lcourtes/ X-Revolutionary-Date: 16 Prairial an 216 de la =?iso-8859-1?Q?R=E9volution?= X-PGP-Key-ID: 0xEA52ECF4 X-PGP-Key: http://www.fdn.fr/~lcourtes/ludovic.asc X-PGP-Fingerprint: 821D 815D 902A 7EAB 5CEE D120 7FBA 3D4F EB1F 5364 X-OS: i686-pc-linux-gnu User-Agent: Gnus/5.11 (Gnus v5.11) Emacs/22.1 (gnu/linux) Cancel-Lock: sha1:WKC8y62tgfQA5Glu2Xp+SnMdyBE= X-detected-kernel: by monty-python.gnu.org: Linux 2.6, seldom 2.4 (older, 4) X-BeenThere: bug-guile@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Bug reports for GUILE, GNU's Ubiquitous Extension Language" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Errors-To: bug-guile-bounces+guile-bugs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.lisp.guile.bugs:3891 Archived-At: Hello, Gregory Marton writes: >> The following message is a courtesy copy of an article >> that has been posted to gmane.lisp.guile.bugs as well. > > Is bug-guile@gnu.org now out of date? I may have to get a > newsreader. Are they mirrored? No, `bug-guile@gnu.org' is not outdated: it's just that I'm posting through Gmane (http://gmane.org/), which is a mail/news bi-directional gateway. The above notice is issued (I think) by Gmane someone is explicitly Cc'd to a newsgroup post. > Nevertheless, it has consistently passed in 1.8.1 and consistently > fails in 1.8.3 with no other changes. Sure, but a quick glance at `NEWS' didn't reveal anything obviously related to the problem at hand. BTW, you might want to even switch to 1.8.5 while you're at it. > call-with-unblocked-asyncs complains: > misc-error: asyncs already unblocked OK, so it's not needed. > With (sleep 0) is no different than without. I just tried and it depends on where you place it. For instance, a `format' call (which also does `SCM_TICK' as a side effect) within the second lambda passed to `ensure' in `with-sigaction' does the trick. The key insight here is that signal delivery in Guile is asynchronous, so you can't know for sure when it will happen. It'd be nice to be able to force system asyncs to run, though. As to why there's such a reproducible difference between 1.8.1 and 1.8.3, maybe you could try using `git-bisect' to find out which change set between tags `release_1-8-1' and `release_1-8-3' introduced the change in behavior. I think it's probably a side-effect of some unrelated change but again, a valid side-effect. Hope this helps, Ludovic.