From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Cc: Gregory Marton <gremio@csail.mit.edu>
Subject: Re: signal handling different in 1.8.3 than 1.8.1?
Date: Tue, 03 Jun 2008 17:07:02 +0200 [thread overview]
Message-ID: <87d4my8smh.fsf@gnu.org> (raw)
In-Reply-To: Pine.LNX.4.64.0806011526420.14410@fiji.csail.mit.edu
Hi,
Gregory Marton <gremio@csail.mit.edu> 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.
next prev parent reply other threads:[~2008-06-03 15:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 19:35 signal handling different in 1.8.3 than 1.8.1? Gregory Marton
2008-06-03 15:07 ` Ludovic Courtès [this message]
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=87d4my8smh.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guile@gnu.org \
--cc=gremio@csail.mit.edu \
/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).