#2699: broken pipe errors are too noisy
---------------------------------+------------------------------------------
Reporter: int-e | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Runtime System | Version: 6.10.1
Severity: normal | Resolution:
Keywords: | Testcase:
Architecture: Unknown/Multiple | Os: Unknown/Multiple
---------------------------------+------------------------------------------
Comment (by int-e):
This is related to #1619 where the silent abortion in the case of broken
pipes got turned into an exception.
It's not quite clear which exception should be silenced. EPIPE becomes an
{{{IOError}}} with type {{{ResourceVanished}}}, but that also includes
several other error conditions, like {{{E_CONNRES}}}. The original
{{{errno}}} number is not contained in {{{IOError}}}; all that's left is
the corresponding value of {{{strerr()}}}, in the {{{ioe_description}}}
field.
Can we get away with filtering {{{IOError { ioe_type = ResourceVanished,
ioe_filename = Just "<stdout>" } }}}? It's a hack though.
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/2699#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
