Re: signal handling different in 1.8.3 than 1.8.1?

[Gregory Marton]

> > They're taking a while to run, but so far all my other tests are also
> > passing in mono-threaded guile 1.8.5
> >  commit 9143131b2766d1e29e05d61b5021395b4c93a6bc Neil Jerram, July 11
>
> Just to be clear: do you mean that they are passing _after_ this
> commit, but were failing _before_?  That's nice to know if so!  What
> are your OS and compiler version?

Hi Neil,

I mean that for every commit between this one and 1.8.0 that I've tested, 
the default compile has failed the tests, and that for both 1.8.1 and this 
commit (I have tested none between) compiling --without-threads makes my 
tests pass.

I would surmise that this is an extremely longstanding issue that was 
introduced some time before 1.8.1, and that I only noticed it now because I 
was trying to use the default build.  I do not assert that it has anything 
at all to do with this particular commit -- I just wanted to let people 
know where my newest endpoint was.  Sorry to be unclear.

I'm running on a modified debian 32-bit architecture. I can't say exactly 
how it's modified because my institution, not I, did the modifications.

However, I have attached again the scheme code to test this condition.  I 
hope it will be helpful in tracking down the issue.  For my own sake, I'm 
happy to use mono-threaded guile.

If you do find the threading issue, I would love it if some version of 
with-timeout were to make it into the guile core.  It's useful.  I 
apologise for letting the copyright assignment issue stall somewhere.  I'll 
look into it again.

Thanks,
Grem

--
------ __@   Gregory A. Marton                http://csail.mit.edu/~gremio/
--- _`\<,_                                                                .
-- (*)/ (*)         Premature optimization is the root of all evil.
~~~~~~~~~~~~~~~~-~~~~~~~~_~~~_~~~~~v~~~~^^^^~~~~~--~~~~~~~~~~~~~~~++~~~~~~~

test-timeout.scm
Description: Text document