From: ludo@gnu.org (Ludovic Courtès)
To: bug-guile@gnu.org
Subject: Re: signal handling different in 1.8.3 than 1.8.1?
Date: Mon, 07 Jul 2008 10:57:58 +0200 [thread overview]
Message-ID: <871w26dqax.fsf@gnu.org> (raw)
In-Reply-To: Pine.LNX.4.64.0807062003110.5333@ashmore.csail.mit.edu
Hi,
Gregory Marton <gremio@csail.mit.edu> writes:
> It turns out I can't find a repository revision where it works. All
> of the major tagged releases fail, including 1.8.1, which makes me
> suspicious, because my Debian-installed guile 1.8.1 continues to work
> (see below). Is there a place to look for Debian's possible
> modifications to guile? Might something else be going on?
IIRC, 1.8.1 was compiled with `--without-threads', so you might want to
try it. Debian-specific modifications are available in the Debian
archive, i.e.,
ftp://ftp.debian.org/debian/pool/main/g/guile-1.8/guile-1.8_1.8.1+1-4.diff.gz .
> I've attached a small test suite that should demonstrate the problem.
> Can anyone else reproduce it? Can anyone else see it pass on 1.8.1 or
> any other version?
With `master':
$ guile ~/tmp/test-timeout.scm
1.9.0
fell asleepoh no, you fell asleep!Expected: outer timeout
Observed: #<unspecified>
outer time has expired, and outer handler is used
> $ libguile/guile ../test-timeout.scm
You should instead use the `pre-inst-guile' script.
Thanks,
Ludovic.
next prev parent reply other threads:[~2008-07-07 8:57 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
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 [this message]
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=871w26dqax.fsf@gnu.org \
--to=ludo@gnu.org \
--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).