#2451: New signal-handling API
---------------------------------+------------------------------------------
Reporter: simonmar | Owner: simonmar
Type: proposal | Status: new
Priority: high | Milestone: 6.14.1
Component: libraries/unix | Version: 6.8.3
Keywords: | Testcase:
Blockedby: | Difficulty: Unknown
Os: Unknown/Multiple | Blocking:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by simonmar):
Replying to [comment:19 phunge0]:
> Really? My (vague) understanding is that a single SIGCHLD might be
generated even though multiple children have exited -- i.e. SIGCHLD will
not be queued the way real-time signals are. I see that w/ a test program
which blocks SIGCHILD w/ sigprocmask -- 2 children exit, only one signal
handler gets invoked.
Hmm, if that's the case then we're in even worse shape than I thought, and
this approach to implementing `System.Process` really won't work at all.
Is there any way to tell that SIGCHLD signals have been dropped?
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2451#comment:20>
GHC <http://www.haskell.org/ghc/>
The Glasgow Haskell Compiler
_______________________________________________
Glasgow-haskell-bugs mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/glasgow-haskell-bugs
