From: Lennon Day-Reynolds <rcoder@...>
Date: 2004-08-14T08:29:02+09:00
Subject: Re: timeouts with threads and SIGALRM

Eric,

It could be the interpreter, or it could be something inside the STAF
library itself trapping SIGALRM, and not letting the events reach the
intepreter (though a testing library that didn't allow you to use
SIGALRM in the code being tested.

However, I really know nothing about STAF, so I couldn't speculate as
to what might be causing the problem. I've never had any problems with
the Kernel.trap method in Ruby before, which is the only reason I keep
leaning towards the bug being elsewhere.

Have the STAF maintainers been able to offer any sense of whether
other language bindings (specifically, I notice they list Python on
the homepage) have had any problems with signal handling?