Hi,
On Wed, 05 Nov 2008 21:57:07 +0900, Bernd Holzmüller <[EMAIL PROTECTED]> wrote:
>>> The attached small example application shows what happens: with
>>> processExecAsync only garbage is shown on both the stdout and the stderr
>>> console window, with processExecAsyncTimed the stdout console works
>>> fine, but the stderr console shows nothing. Main.hs is the wxHaskell GUI
>>> with two buttons, both calling the application compiled from
>>> Testproc.hs, one using processExecAsync, one using the Timed variant.
>>> The attached makefile builds everything.
I tested Mads' program on Mac OS X platform.
[1]. processExecAsync example crashes this program.
[2]. processExecAsyncTimed example doesn't work correctory. stdout console works
fine, but the stderr console *almost* shows nothing. We must care about
this
fact. stderr console *sometimes* works fine.
(I also saw this fact on Windows. stderr console *sometimes* works fine,
too.)
[3]. wxExecProcess example works fine.
>>> I am developing a test management GUI where processes are started and
>>> their output (on stdout and stderr) are shown on corresponding console
>>> windows. The process management worked quite OK with version 0.9.4 but
>>> does no longer work in version 0.10.3 (using ghc 6.8.3 on Windows XP).
> I applied your supposal on my Windows machine with the following
> results: wxExecProcess now indeed yields output on stderr, but output on
> both stdout and stderr are somewhat incomplete (with no change when
> setting output buffering in processtest.exe to NoBuffering):
>
> (snip)
Do you test program with same version's GHC? GHC's IO functions has some bugs
on Windows platform. So, I want to know that this is wxHaskell's bug or GHC's
bug.
http://hackage.haskell.org/trac/ghc/ticket/806
http://hackage.haskell.org/trac/ghc/ticket/2189
etc...
I tried to fix the problem in this week. But I can't find where causes this
problem by undoing Graphics.UI.WXCore.Process related changes.
Best Regards,
> display on stdout frame:
>
> Stdout: 100: Info
> 98: Info
> 96: Info
> 94: Info
> 92: Info
> 90: Info
> 88: Info
> 86: Info
> 84: Info
> 82: Info
> Stdout:
> 80: Info
> 78: Info
> ...
>
> and on stderr frame:
>
> Stderr: 99: Error
> 97: Error
> 95: Error
> 93: Error
> 91: Error
> 89: Error
> 87: Error
> 85: ErroStderr: r
> 83: Error
> ...
>
> That is, the first 8 bytes (Stdout: / Stderr: ) are most of the time
> vanished. Whereas processExecAsyncTimed yields the correct output (of
> course only on stdout):
>
> Stdout: 100: Info
> Stdout: 98: Info
> Stdout: 96: Info
> Stdout: 94: Info
> ...
--
shelarcy <shelarcy hotmail.co.jp>
http://page.freett.com/shelarcy/
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
wxhaskell-devel mailing list
wxhaskell-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wxhaskell-devel
