Re: [wxhaskell-devel] Application hangs when using processExecAsyncTimed

[shelarcy <she...@gm...>]

Hi Mads,

On Tue, 27 May 2008 04:00:31 +0900, Mads Lindstrøm <mad...@ya...> wrote:
> Have you actually observed that this is problem in the specific case
> with processExecAsyncTimed?
>
> I am asking because if you have observed it at windows, then what I
> thought was a Linux-only issue is also a Windows issue. After all, the
> putStrLn only happens in case of an error (negative unicode).

I can't reproduce that error in my environment with command (I don't
use Graphics.UI.WXCore.Process usually. So, I don't know which command
reproduces error). But I think this is not only Linux problem but also
all platform that use before wxWidgets 2.8.x.

Because wxWidgets Change Log writes following:

- wxInputStream::GetC() now returns an int in the range 0 - 255 on success
   instead of a char the range -128 - 127.

You can see this message in wxWidgets-*.*.*/docs/changes.txt.
Or below URL

http://slackblogs.blogspot.com/2006/12/wxwidgets-280.html


Best Regards,


> shelarcy wrote:
>> Hi,
>> I'm sorry about my reply is late.
>>
>> On Thu, 15 May 2008 17:15:54 +0900, Eric Y. Kow <eri...@gm...> wrote:
>> > Shelarcy: any ideas?
>>
>> I found Mad's previous patch left an problem for Windows platform.
>>
>> http://article.gmane.org/gmane.comp.lang.haskell.wxhaskell.general/423
>>
>> Windows' stdout, stdin and stdout requires console. But we can build
>> wxHaskell GUI program without console by -optl-mwindows option. So,
>> withCharResult's "hPutStrLn stderr" causes problem. I fixed this problem
>> by using Debug.Trace.putTraceMsg instedad of hPutStrLn stderr.

-- 
shelarcy <shelarcy    hotmail.co.jp>
http://page.freett.com/shelarcy/