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 17:07:02 +0200 Message-ID: <87d4my8smh.fsf@gnu.org> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1212505713 14306 80.91.229.12 (3 Jun 2008 15:08:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Tue, 3 Jun 2008 15:08:33 +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 17:09:14 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 1K3Y8D-00047F-R9 for guile-bugs@m.gmane.org; Tue, 03 Jun 2008 17:09:02 +0200 Original-Received: from localhost ([127.0.0.1]:50892 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3Y7R-0005OP-Ic for guile-bugs@m.gmane.org; Tue, 03 Jun 2008 11:08:13 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1K3Y6X-0004xr-Dr for bug-guile@gnu.org; Tue, 03 Jun 2008 11:07:17 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1K3Y6V-0004wr-EN for bug-guile@gnu.org; Tue, 03 Jun 2008 11:07:16 -0400 Original-Received: from [199.232.76.173] (port=37930 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1K3Y6U-0004wR-W8 for bug-guile@gnu.org; Tue, 03 Jun 2008 11:07:15 -0400 Original-Received: from main.gmane.org ([80.91.229.2]:45816 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 1K3Y6V-0004fc-GI for bug-guile@gnu.org; Tue, 03 Jun 2008 11:07:15 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1K3Y6Q-0001Wa-HW for bug-guile@gnu.org; Tue, 03 Jun 2008 15:07:10 +0000 Original-Received: from 193.50.110.83 ([193.50.110.83]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Jun 2008 15:07:10 +0000 Original-Received: from ludo by 193.50.110.83 with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 03 Jun 2008 15:07:10 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 35 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: 193.50.110.83 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:1V1ReFjyBdEtKwa2wnAlfymAyts= 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:3889 Archived-At: Hi, Gregory Marton writes: > Now that I've upgraded to 1.8.3 from 1.8.1, some old test cases are > failing. In particular: According to `NEWS', there were no signal-related changes. > (define (ensure body-lambda ensuring-lambda) > (dynamic-wind > (lambda () #t) > body-lambda > ensuring-lambda)) > > (define (with-sigaction signum handler flags lamb) > (let ((old-sigaction (sigaction signum))) > (if flags (sigaction signum handler flags) (sigaction signum handler)) > (ensure > lamb > (lambda () > (sigaction signum (car old-sigaction) (cdr old-sigaction)))))) Signal handlers are invoked asynchronously as system asyncs, and system asyncs are run whenever `SCM_TICK' is encountered in the C code. There doesn't seem to be any Scheme procedure to force the execution of system asyncs, but maybe you can try invoking LAMB above in `call-with-unblocked-asyncs' and/or adding a `(sleep 0)' right before it to force the execution of pending system asyncs. Let us know if it helps. Thanks, Ludovic.