#3890: runghc sometimes won't allow redirecting of stdout/stderr
---------------------------------+------------------------------------------
Reporter: simonmic | Owner:
Type: bug | Status: new
Priority: normal | Milestone:
Component: Runtime System | Version: 6.10.4
Keywords: | Difficulty:
Os: Unknown/Multiple | Testcase:
Architecture: Unknown/Multiple | Failure: None/Unknown
---------------------------------+------------------------------------------
Description changed by igloo:
Old description:
> See attached test.hs. Here's stdout working normally:
>
> $ runhaskell test.hs | cat
> output
> $
>
> But after uncommenting either the cmdArgs line or the defaultMainWithArgs
> line, stdout can't be captured:
>
> $ runhaskell test.hs | cat
> $
>
> It does appear on the console if you don't redirect though. The same goes
> for stderr. This prevents me testing uncompiled scripts with
> shelltestrunner. I'm on mac os 10.5.
New description:
See attached test.hs. Here's stdout working normally:
{{{
$ runhaskell test.hs | cat
output
$
}}}
But after uncommenting either the cmdArgs line or the defaultMainWithArgs
line, stdout can't be captured:
{{{
$ runhaskell test.hs | cat
$
}}}
It does appear on the console if you don't redirect though. The same goes
for stderr. This prevents me testing uncompiled scripts with
shelltestrunner. I'm on mac os 10.5.
--
--
Ticket URL: <http://hackage.haskell.org/trac/ghc/ticket/3890#comment:3>
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
