Signals are not delivered for corresponding events #224
Labels
bug
Something isn't working
fixed-in-2022.1
issue is fixed in the 2022.1 release
gforge
bug (or feature request) ported from smlnj-gforge repository
Version
110.85/110.98.1
Operating System
OS Version
other Windows 10
Processor
x86 (32-bit)
Component
Other
Severity
Major
Description of the problem
No sigALRM nor sigGC will be delivered to installed handlers,
when an interval timer is set by "setIntTimer" or
garbage collection is enforced by "doGC".
The behavior is the same in 110.85 for Windows 10 (pasted as
atranscript), 110.98.1 (both the 32/64 version) for Linux.
Additional comments:
As for sigGC, it has been reported in #65.
Transcript
Expected Behavior
No response
Steps to Reproduce
open Signals
open SMLofNJ.IntervalTimer
open SMLofNJ.Internals.GC;
fun laterSec x = let open Time in now() + fromSeconds x end ;
fun prt x = (TextIO.output(TextIO.stdOut,x); TextIO.flushOut TextIO.stdOut);
val _ = setHandler (sigALRM, HANDLER(fn z => (prt "tm";#3 z) )) ;
val _ = setHandler (sigGC , HANDLER(fn z => (prt "gc";#3 z) )) ;
unmaskSignals (MASK [sigALRM, sigGC]);
val _ = setIntTimer (SOME (laterSec 10)); (* nothing will happen )
val _ = doGC 10; ( also nothing happens *)
Additional Information
No response
Email address
saitohm@sun.ac.jp
Comments from smlnj-gforge
Original smlnj-gforge bug number 291
Submitted via web form by Masaya Saito saitohm@sun.ac.jp on 2021-18-15 at 11:1800
Keywords: structure Signals
comment by @JohnReppy on 2022-04-01 23:0400 +000 UTC
Also see #65
comment by @JohnReppy on 2022-44-27 15:4400 +000 UTC
I was not able to reproduce the problem with
sigALRM
(it works for me), but support forsigGC
has been added in 110.99.3 and 2022.1.The text was updated successfully, but these errors were encountered: