From: Gregory Marton <gremio@csail.mit.edu>
To: bug-guile@gnu.org
Subject: signal handling different in 1.8.3 than 1.8.1?
Date: Sun, 1 Jun 2008 15:35:40 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0806011526420.14410@fiji.csail.mit.edu> (raw)
Hi folks,
Now that I've upgraded to 1.8.3 from 1.8.1, some old test cases are
failing. In particular:
(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))))))
;; imagine an appropriate (assert bool message) and (assert-equal a b msg)
(let ((orig (sigaction SIGALRM))
(sigcalled #f))
(with-sigaction
SIGALRM (lambda (sig) (set! sigcalled #t)) #f (lambda () (raise SIGALRM)))
(assert sigcalled "we set and handled an alarm")) ;; FAILS in 1.8.3
(assert-equal orig (sigaction SIGALRM) "returned to the original state")
(let ((outer "nop")
(inner "nop"))
(with-sigaction
SIGALRM (lambda (sig) (set! outer "outer")) #f
(lambda ()
(with-sigaction
SIGALRM (lambda (sig) (set! inner "inner")) #f
(lambda ()
(raise SIGALRM)))
(raise SIGALRM)))
(and (assert-equal "inner" inner "inner sig got handled") ;; FAILS
(assert-equal "outer" outer "outer sig got handled")))
(assert-equal orig (sigaction SIGALRM) "returned to the original state")
All of these passed in 1.8.1. If this is no longer The Recommended Way,
how would one go about it?
Many thanks,
Grem
--
------ __@ Gregory A. Marton http://csail.mit.edu/~gremio/
--- _`\<,_ .
-- (*)/ (*) Lots of Insidious Silly Parentheses (LISP :-)
~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~++~~~~~~~
next reply other threads:[~2008-06-01 19:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 19:35 Gregory Marton [this message]
2008-06-03 15:07 ` signal handling different in 1.8.3 than 1.8.1? Ludovic Courtès
2008-06-03 16:05 ` Gregory Marton
2008-06-03 20:32 ` Ludovic Courtès
2008-06-06 19:37 ` Gregory Marton
2008-06-06 19:56 ` Gregory Marton
2008-06-07 10:38 ` Ludovic Courtès
[not found] ` <Pine.LNX.4.64.0806260936100.31255@ashmore.csail.mit.edu>
[not found] ` <87bq1ngvw7.fsf@gnu.org>
2008-06-27 19:05 ` Gregory Marton
2008-06-28 18:09 ` Ludovic Courtès
2008-06-29 17:45 ` Gregory Marton
2008-06-29 18:02 ` Gregory Marton
2008-06-29 18:06 ` Gregory Marton
2008-06-30 7:38 ` Ludovic Courtès
2008-07-07 0:30 ` Gregory Marton
2008-07-07 8:57 ` Ludovic Courtès
2008-07-17 12:08 ` Gregory Marton
2008-07-17 12:37 ` Ludovic Courtès
2008-07-17 15:24 ` Gregory Marton
2008-07-17 15:51 ` Ludovic Courtès
2008-07-17 15:59 ` Gregory Marton
2008-07-17 20:47 ` Neil Jerram
2008-07-17 22:11 ` Gregory Marton
2008-07-18 8:18 ` Ludovic Courtès
2008-07-18 11:23 ` Gregory Marton
2008-07-18 12:02 ` Ludovic Courtès
2008-07-18 13:44 ` with-timeout and asynchronous alarm (was: signal handling different in 1.8.3 than 1.8.1?) Gregory Marton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.64.0806011526420.14410@fiji.csail.mit.edu \
--to=gremio@csail.mit.edu \
--cc=bug-guile@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).