#2301: Proper handling of SIGINT/SIGQUIT
------------------------------------------+---------------------------------
Reporter: duncan | Owner:
Type: bug | Status: new
Priority: normal | Milestone: 7.0.2
Component: libraries/process | Version: 6.12.3
Resolution: | Keywords:
Testcase: | Blockedby:
Difficulty: Unknown | Os: Unknown/Multiple
Blocking: | Architecture: Unknown/Multiple
Failure: Incorrect result at runtime |
------------------------------------------+---------------------------------
Changes (by simonmar):
* os: MacOS X => Unknown/Multiple
* architecture: x86 => Unknown/Multiple
Comment:
@mcandre: this is the documented behaviour. From `System.Exit.exitWith`:
{{{
-- Note: in GHC, 'exitWith' should be called from the main program
-- thread in order to exit the process. When called from another
-- thread, 'exitWith' will throw an 'ExitException' as normal, but the
-- exception will not cause the process itself to exit.
}}}
This ticket is about something different: the behaviour of SIGINT/SIGQUIT
when there are child processes started by the Haskell program.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2301#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
