#2301: Proper handling of SIGINT/SIGQUIT
---------------------------+------------------------------------------------
Reporter: duncan | Type: bug
Status: new | Priority: normal
Milestone: 6.14.1 | Component: libraries/process
Version: 6.8.2 | Keywords:
Testcase: | Blockedby:
Difficulty: Unknown | Os: Unknown/Multiple
Blocking: | Architecture: Unknown/Multiple
Failure: None/Unknown |
---------------------------+------------------------------------------------
Comment(by phunge0):
Replying to [comment:9 diego]:
> And when describing exec POSIX says:
> > Signals set to the default action (SIG_DFL) in the calling process
image shall be set to the default action in the new process image.
> > Except for SIGCHLD, signals set to be ignored (SIG_IGN) by the calling
process image shall be set to be ignored by the new process image.
> > Signals set to be caught by the calling process image shall be set to
the default action in the new process image (see <signal.h>).
>
> Thus, to avoid breaking applications that rely on the the default
handler of SIGPIPE the RTS should restore the handler before starting new
processes.
>
> I can't say how many applications are affected by this nowadays. Simple
applications may rely on default bahavior of signals. But it seems to be a
minor issue.
I think this detail needs fixing too, here's a patch as an RFC:
http://www.haskell.org/pipermail/glasgow-haskell-
users/2010-August/019082.html
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2301#comment:14>
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
