> So it looks like the alarm isn't killing the eval before the while > terminates.
Weird. I wonder if this will happen in pure C code that does a similar busy wait. It may have to do with delayed signal delivery or such at the UML level. -R
> So it looks like the alarm isn't killing the eval before the while > terminates.
Weird. I wonder if this will happen in pure C code that does a similar busy wait. It may have to do with delayed signal delivery or such at the UML level. -R