> On Mon, Oct 09, 2000 at 01:42:45PM +0200, Volker Stolz wrote:
> > It seems that in 4.08 & 4.08.1 signal handling still seems
> to be flawed:
>
> I forgot to mention that this only happens when using job-control:
>
> 1) start the program
> 2) use Ctrl-Z to suspend
> 3) kill -USR1
> 4) fg to resume, sigUSR1-handler is invoked,
> the programm still works(!)
> 5) sending another USR1 -- no matter if suspending or using another
> shell to issue the kill ! -- will yield the hGetChar-error.
>
> Conclusion: This only seems to happen when the program is
> suspended and
> receives a signal (it seems any signal will do, I tried
> sigPIPE, too, in
> step #3, for which I installed an ignore-handler). On
> receiving the 2nd
> signal regardless of being still suspended or not the hGetChar fails.
Ok. Is it possible to cut down the example to maybe 2 concurrent threads,
so we could try to fix the problem here? There aren't any obvious bugs in
the signal handling code (at least, not obvious to me :).
Cheers,
Simon
_______________________________________________
Glasgow-haskell-bugs mailing list
[EMAIL PROTECTED]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
