#4162: GHC API messes up signal handlers
---------------------------------+------------------------------------------
Reporter: jcpetruzza | Owner:
Type: bug | Status: new
Priority: normal | Component: GHC API
Version: 6.12.3 | Keywords:
Os: Unknown/Multiple | Testcase:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Comment(by carlhowells):
If anyone with knowledge of the GHC api could chime in, I'd greatly
appreciate it. I'm waiting on an update to the hint package, which is
waiting on a response to this.
This comes down to two things, fundamentally:
1) It's a bug that the GHC api changes signal handlers, and doesn't change
them back when it's finished. The GHC api probably shouldn't even touch
signal handlers. The handler it's installing is part of GHCi, not the GHC
api. Hence I believe GHCi code should be installing it, not the GHC api.
2) Given the current behavior, is it a safe workaround to restore the
previous signal handlers inside the action runGhc is performing, or should
restoring them be delayed until runGhc returns?
An answer to the latter is what's required for forward progress on hint.
The former is less urgent, but should be considered a bug to some degree
in the GHC api.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/4162#comment:1>
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
