#1619: The RTS chokes on SIGPIPE (happens with runInteractiveCommand)
-------------------------------+--------------------------------------------
Reporter: int-e | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Runtime System | Version: 6.7
Severity: normal | Resolution:
Keywords: | Difficulty: Unknown
Os: Linux | Testcase:
Architecture: x86 |
-------------------------------+--------------------------------------------
Comment (by int-e):
I had hoped for a little more shielding by the RTS, especially since
{{{System.Posix.Signals}}} isn't universally available. And I'd really
like the above program to print {{{"after"}}} as well. A descriptive
exception would be a bonus.
But I realize now that it's a design decision. If you want to provide
POSIX semantics by default then you can't ignore the signal. I'm not sure
what the least surprising behaviour is -- although obviously the current
behaviour surprised me enough to declare it a bug :)
Turning fatal signals into exceptions sounds neat, but is tricky to get
right. You have to assure that the exceptions are delivered promptly.
That requires forcibly interrupting a running thread, which the RTS
currently can't do, as far as I know (it waits until the next allocation
or for certain primops). Oh and FFI will cause trouble as well.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/1619>
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
